The case for disaggregated LLM serving
The KV cache for a request is produced all at once during prefill, then consumed token by token during decode, so it's a natural place to cut the workload in two.. People usually think about it as a tool to tune time-per-output-token (TPOT) and time-to-first-token (TTFT) SLOs independently. I want to argue that, in practice, with sufficient load, and modulo many important implementation difficulties, you should always disaggregate.
- ▪The KV cache for a request is produced all at once during prefill, then consumed token by token during decode, so it's a natural place to cut the workload in two..
- ▪People usually think about it as a tool to tune time-per-output-token (TPOT) and time-to-first-token (TTFT) SLOs independently.
- ▪I want to argue that, in practice, with sufficient load, and modulo many important implementation difficulties, you should always disaggregate.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,565 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Doubleword |
| Canonical URL | https://blog.doubleword.ai/when-to-disaggregate |
| Publication time | Wed, 12 Aug 2026 08:46:51 +0000 |
| Retrieval time | 2026-08-12T08:51:30.355Z |
| Last seen | 2026-08-12T08:51:30.355Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | TyOVOcRFW35l · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
←August 11, 2026Inference APIAPIThe case for disaggregated LLM servingFergus FinnFounder & Member of Technical Staff, DoublewordContentsWhat is disaggregated prefillHow to rate balanceThe conditions under which we can disaggregate properlyThe load vs. quantization effectsThe fabric sustains the KV cache production rateThe traffic balance can be trackedWhy it's strictly better, once the conditions are metConclusionAppendix: Space & UtilizationThe HBM tax that does existAttention-FFN disaggregationDisaggregated inference is an inference optimization technique in which we run prefill and decode on separate GPU pools, and ship the KV cache between them over the networkFirst laid out in DistServe and Splitwise.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Doubleword.