<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Latency on </title>
    <link>https://hiren.me/tags/latency/</link>
    <description>Recent content in Latency on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 12:00:00 -0700</lastBuildDate>
    <atom:link href="https://hiren.me/tags/latency/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Inference in production (part 5): workload types</title>
      <link>https://hiren.me/posts/inference-in-production-part-5/</link>
      <pubDate>Sat, 03 Oct 2026 12:00:00 -0700</pubDate>
      <guid>https://hiren.me/posts/inference-in-production-part-5/</guid>
      <description>&lt;p&gt;The first four parts covered &lt;a href=&#34;https://hiren.me/posts/inference-in-production-part-1/&#34; &gt;prefill and decode pools&lt;/a&gt;, &lt;a href=&#34;https://hiren.me/posts/inference-in-production-part-2/&#34; &gt;the gateway, router and autoscaler&lt;/a&gt;, &lt;a href=&#34;https://hiren.me/posts/inference-in-production-part-3/&#34; &gt;hardware failures&lt;/a&gt; and &lt;a href=&#34;https://hiren.me/posts/inference-in-production-part-4/&#34; &gt;rollouts&lt;/a&gt;. They mostly assumed one kind of traffic, a user chatting. A coding agent, a reasoning model and an overnight batch job send very different requests, and some of the machinery from those posts matters less for them, or more.&lt;/p&gt;&#xA;&lt;p&gt;This part describes a workload with a few numbers, goes through the common types, and then goes back through parts 1 to 4 to see which workloads each piece is for. The last section measures, on one H100, how much a few long prompts slow down everyone else&amp;rsquo;s answers, and which latency numbers show it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
