paper web signal

OasisKV cuts KV cache 6.5-9.7x, lifts vLLM decode 2.1x

TL;DR

  • OasisKV keeps only the most relevant KV entries in HBM and prefetches the rest from host or remote memory before each decode step.
  • Authors report 1.69× throughput over dense vLLM on reasoning workloads and up to 2.1× on multi-GPU long-context serving.
  • Accuracy stays within 0.7 points of full attention at a 2,048-token KV budget, using 6.5–9.7× less KV transfer.

Something has quietly shifted in how researchers talk about the LLM inference bottleneck. It is no longer compute, it is the KV cache. A new paper on arXiv from a team including Can Xiao, Yiren Zhao and Yongqiang Xiong argues the fix is not a bigger GPU but a smarter one. Keep only the KV entries you actually need in HBM, and stream the rest in from host or remote memory just before the decode step asks for them.

The system, called OasisKV, wires this together with three moving parts. Sparse KV storage holds only the most relevant tokens in HBM. A lookahead predictor, borrowed from speculative decoding, guesses which KV blocks will matter next. A background prefetch pipeline pulls those blocks in ahead of the attention computation. The authors report the approach transfers 6.5–9.7× less KV than full-transfer baselines, gets 1.69× throughput over dense vLLM on reasoning workloads at a 0.1 accuracy loss, and up to 2.1× on multi-GPU long-context serving, all while staying within 0.7 points of full attention at a 2,048-token KV budget.

If those numbers hold on real customer workloads, the practical implication is that a lot of the HBM operators have been buying to keep long contexts hot may not be necessary. That matters most for teams running long-context reasoning, agents with big scratchpads, and multi-turn workloads where the KV cache dominates the memory footprint rather than the model weights.

A few caveats worth flagging. This is an August 2026 arXiv submission, not peer reviewed, and the numbers come from a single implementation on vLLM. The abstract does not name which model families the accuracy comparison was measured against, and it is silent on how the prefetch pipeline degrades when the speculative lookahead guesses wrong on adversarial inputs. Anyone tempted to rebuild an inference stack around this should reproduce the throughput claim on their own traffic before assuming the 2.1× carries over.

Still, if the KV cache really is the binding constraint rather than compute, the inference providers who win the next round will be the ones pairing sparse attention with fast tiered memory. Being built on vLLM makes this technique straightforward for the broader ecosystem to pick up if the authors upstream it.