#KV cache

13 stories · 4 in 7 days · 11 in 30 days
Stories, products and papers tagged "KV cache", newest first.
Oct 22
PapersBuildersSelected02:05
AKV: Agents Manage Their Own KV Cache to Cut LLM Costs

This reframes context engineering as a systems problem: instead of editing the visible prompt, the agent rewrites its own cache, avoiding the re-prefill penalty that summarization triggers. Teams building long-running agents with multi-turn tool calls can cut serving cost measurably without changing what the model sees. The gains apply to any stack serving LLMs with prefix caching, such as vLLM-based deployments.

DAIR.AI@dair_aiSource
Oct 21
ProductsBuildersMulti-sourceSelected01:23
vLLM Project Shows KV Cache and Kernel Optimizations at PyTorchCon 2026

vLLM now spans three hardware ecosystems, which reduces the lock-in that previously tied inference stacks to NVIDIA GPUs. Teams running self-hosted inference can benchmark vLLM against vendor-specific runtimes on AMD and TPU infrastructure. The KV cache management work matters most for serving long-context models where memory, not compute, is the bottleneck.

Event
官方账号PyTorch@PyTorch11 sourcesSource
Oct 20
How-toBuildersOfficialSelected00:28
vLLM push-based NIXL connector cuts TTFT in disaggregated inference

Shifting KV-cache transfer coordination off the critical path removes a hidden latency tax in prefill-decode disaggregation, and the 3x TTFT gain applies to any team serving LLMs at scale on vLLM. Practitioners running inference on AWS can adopt the NIXL connector on EC2 P5en with EFA networking directly from the guide. Compared with pull-based transfer, the push design needs no receiver-side polling, which is what unlocks the latency savings.

官方一手AWS Machine Learning Blog@Sunita NadampalliSource
Oct 18
How-toBuildersSelected21:24
Stanford CS336 Lecture 10 Covers LLM Inference Optimization

Percy Liang's closing argument reframes the KV cache as the structural root of Transformer inference inefficiency, pointing to architectures designed for inference from day one, such as SSMs, linear attention, and diffusion-based non-autoregressive generation. Engineers building or tuning inference stacks get a single coherent map from architecture to serving systems. The executable lecture notes with sympy-verified formulas make the material directly reproducible rather than slide-level theory.

Event
shao__meng@shao__meng2 sourcesSource
Oct 15
Oct 12
PapersBuildersSelected22:20
Paper Tests Multi-Agent Systems With Persistent Memory on Long-Context Work

The finding suggests viral multi-agent memory demos may not transfer to standard evaluation setups, since benchmarks are structured in ways that neutralise recall benefits. Engineers deciding whether to add persistent memory to agent pipelines should weigh the near-zero measured accuracy gain against its efficiency advantages. The paper's benchmark-design critique is a useful checklist when validating similar architectures.

elvis@omarsar0Source
Oct 9
ProductsBuildersMulti-sourceSelected03:04
NVIDIA Dynamo targets KV-cache reuse for agentic serving

KV-cache reuse, not model quality, may become the bottleneck for agent products at scale, since idle context still occupies memory while agents wait on tool calls. Engineers building multi-step agent backends can use Dynamo's router-plus-cache-manager design as a reference for cutting serving cost without adding GPUs. It competes in the same layer as vLLM and SGLang-style serving stacks.

Event
官方账号PyTorch@PyTorch11 sourcesSource
Oct 8
ModelsBuildersSelected09:59
vLLM Highlights DeepSeek-V4.1-Flash SWA Optimization

SWA bounded replay shows how KV-cache reuse for agent loops can be engineered around sliding-window attention, a pattern many teams will copy as agent traffic grows. Engineers running agent stacks on vLLM can apply it to reduce TTFT under high concurrency. The writeup also signals that DeepSeek-V4.1-Flash inference performance is being actively tuned by the community rather than relying on the lab alone.

官方账号vLLM@vllm_projectSource
PapersBuildersSelected02:15
Nanbeige 4.2 Looped Transformer Breakdown Compares Weight Reuse

The three reuse tricks all called 'looped transformers' differ in cache behaviour and cost, and picking the wrong one can burn a training week or budget a 3B decode like a 3B file. Builders planning efficient architectures can use this to decide whether extra loops justify their compute and whether a second cache is needed. Nanbeige 4.2 offers a concrete open reference point against standard Transformers.

官方账号AlphaSignal@AlphaSignalAISource
Oct 6
PapersBuildersSelected13:42
Fixed-Point Training Speeds Up Looped Language Models

The key insight is that near-fixed-point recurrent states make much of the compute spent on full backpropagation and full KV caches redundant, cutting costs across training, decoding and RL at once. Practitioners building efficient inference stacks or RL pipelines for recurrent models can apply KV sharing and distilled prefill directly. Compared with Huginn's fixed prior, the learned prior plus orthogonal injection improves perplexity at every scale tested up to 1.6B parameters.

arXiv cs.LG@Benhao Huang et al. (7)Source
Sep 23
Sep 11