KV cache often spills out of HBM in the agentic era, tanking effective bandwidth
AccBalanced · x · 2026-09-06
A rebuttal to the view that inference performance tracks HBM pin bandwidth alone:
- The bandwidth argument only holds when the KV cache always fits in HBM. In the agentic era of long contexts and multi-turn tasks, it often doesn't.
- Once capacity runs out, tokens offload to slower DRAM/NAND tiers and latency spikes.
- In a tiered memory system, capacity and bandwidth are inseparable: HBM is the fast lane, and capacity is what keeps it from clogging. Cutting HBM capacity sacrifices the very bandwidth you thought you saved.
More from Infra
- SurfSense: an open-source local NotebookLM with MCP agents and a prompt-caching lesson — FurtiveMirth · 2026-10-23
- Meta researcher: horrifying infra, not talent, is why OSS can't catch closed frontier — A_K_Nain · 2026-10-23
- Jane Street and NVIDIA speed up Mamba-2 with custom cuTile kernels — blelbach · 2026-10-23
- LatentLoop: asymmetric compute allocation cuts looped-MoE training cost by 19% — pmttyji · 2026-10-23
- Same AI request emits 8.5x more CO2 in Texas than in Sweden — jlundberg · 2026-10-23
- SK Hynix Pulls Plug on Solidigm US IPO as Chip Stocks Slide, Shares Down ~30% This Quarter — rohanpaul_ai · 2026-10-23