The KV Cache Tax: Why Inference Servers Run Out of Memory Before Compute
You sized your cluster for the weights, the optimizer states, and the gradients, and once the model was trained, the memory math felt settled. Serving looked cheap by comparison: load the weights, run forward passes, done.Then you put the model behind real traffic, and it fell over at a load that made no sense.I was sizing an inference deployment for a mid-sized model on a shared GPU pool. The weights fit with room to spare, and the server ran fine in testing.
- ▪You sized your cluster for the weights, the optimizer states, and the gradients, and once the model was trained, the memory math felt settled.
- ▪Serving looked cheap by comparison: load the weights, run forward passes, done.Then you put the model behind real traffic, and it fell over at a load that made no sense.I was sizing an inference deployment for a mid-sized model on a shared
- ▪The weights fit with room to spare, and the server ran fine in testing.
Towards Data Science files mainly under ai. We currently carry 150 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 | Towards Data Science |
| Canonical URL | https://towardsdatascience.com/the-kv-cache-tax-why-inference-servers-run-out-of-memory-before-compute/ |
| Publication time | Wed, 16 Sep 2026 12:30:02 GMT |
| Retrieval time | 2026-09-16T12:33:41.407Z |
| Last seen | 2026-09-16T12:33:41.407Z |
| 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 | f1KakhNyiInK · 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
AI InferenceThe KV Cache Tax: Why Inference Servers Run Out of Memory Before ComputeA VRAM budget formula for LLM serving, and three optimization strategies mapped to the traffic patterns that trigger the OOM.Mostafa IbrahimSeptember 16, 20268 min readImage by authorThe Model Fits, the Requests Don'tVRAM used to be a training-time worry. You sized your cluster for the weights, the optimizer states, and the gradients, and once the model was trained, the memory math felt settled. Serving looked cheap by comparison: load the weights, run forward passes, done.Then you put the model behind real traffic, and it fell over at a load that made no sense.I was sizing an inference deployment for a mid-sized model on a shared GPU pool.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Towards Data Science.
Discussion
0 commentsMore from Towards Data Science
