<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Graviton on ferkakta.dev</title><link>https://ferkakta.dev/tags/graviton/</link><description>Recent content in Graviton on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Mon, 16 Mar 2026 10:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/graviton/index.xml" rel="self" type="application/rss+xml"/><item><title>I was guessing build times from my laptop. A six-cent spot instance proved me wrong.</title><link>https://ferkakta.dev/spot-instance-benchmarking/</link><pubDate>Mon, 16 Mar 2026 10:00:00 -0600</pubDate><guid>https://ferkakta.dev/spot-instance-benchmarking/</guid><description>&lt;p&gt;I needed to know how fast a 16GB Docker image builds on Graviton. The image is a Docling container — document intelligence, heavy Python dependencies, big model downloads. I was sizing a self-hosted runner for CI and needed real numbers: build duration, peak memory, CPU profile. The numbers would determine whether I could get away with an r6g.large or needed to step up to an xlarge.&lt;/p&gt;
&lt;p&gt;I did what everyone does first. I ran the build on my laptop.&lt;/p&gt;</description></item></channel></rss>