<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>H100 on </title>
    <link>https://hiren.me/tags/h100/</link>
    <description>Recent content in H100 on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 24 Sep 2026 15:54:50 -0700</lastBuildDate>
    <atom:link href="https://hiren.me/tags/h100/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Watching a KV cache grow (part 3): move it or rebuild it?</title>
      <link>https://hiren.me/posts/watching-a-kv-cache-grow-part-3/</link>
      <pubDate>Thu, 24 Sep 2026 15:54:50 -0700</pubDate>
      <guid>https://hiren.me/posts/watching-a-kv-cache-grow-part-3/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://hiren.me/posts/watching-a-kv-cache-grow/&#34; &gt;Part 1&lt;/a&gt; showed what a KV cache is as bytes: 23,040 per token for SmolLM2-135M. &lt;a href=&#34;https://hiren.me/posts/watching-a-kv-cache-grow-part-2/&#34; &gt;Part 2&lt;/a&gt; showed that decode gets slower as the cache grows, because every step has to move it through memory.&lt;/p&gt;&#xA;&lt;p&gt;Where I&amp;rsquo;m heading with this series is disaggregated inference. The idea is to run prefill on one set of GPUs and decode on another, because the two phases want different things (parts 1 and 2 are really about that difference). The catch is that the cache prefill builds has to get from the prefill machine to the decode machine before decoding can start.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
