KV-cache compression
H2O
H$_2$O: Heavy-Hitter Oracle for Efficient Generative Inference of Large Language Models
Heavily superseded — a standard baseline that newer methods routinely beat
65 papers critique it · 56 beat it on benchmarks
What papers say
Verbatim critique sentences, each from a paper that cites H2O as a baseline.
under unidirectional mask in LLM computations, aggregating attention weights across all query states often causes recent KV cache elements to be mistakenly evicted, degrading the quality of subsequent generations
“However, these methods depend on attention scores for eviction, requiring CUDA kernel modifications to track them.”
“the majority of studies adopt cumulative attention scores as the criterion for token pruning”
“While such techniques effectively reduce the pressure on memory bandwidth during the attention computation, they typically do not reduce the physical storage requirements of the KV cache; the full context remains resident in memory, even if only a fraction is accessed during decode.”
“Existing approaches use heuristics like discarding oldest tokens~fastgen, streamingllm or leverage attention scores from past queries~h2o, snapkv, tova, but these strategies are limited for real-world scenarios”
“these methods rely on predefined retention rules and cannot adapt to evolving inference dynamics”
“Although these methods generally have low additional overhead, they often lead to noticeable performance degradation.”
“Methods such as SnapKV li2024snapkv and H2O zhang2024h2o apply this strategy to vision-language modeling (VLM) tasks by treating visual and text tokens uniformly across long sequences during pruning. Unfortunately, these methods rely on original attention scores that mix different modalities, potentially leading to suboptimal pruning outcomes.”
“these methods either (i) optimize throughput while leaving allocation semantics untouched or (ii) assume a monolithic, forward-moving path, failing to model the topological constraints and frequent backtracking inherent in tree-structured search”
“post-hoc compression algorithms usually evict KV pairs based on attention scores, which is not compatible with FlashAttention and thus prevents their applications in modern LLMs inference systems.”
“H2O and StreamingLLM allocate the same cache budget across all layers, causing denser layers to miss important tokens in the context, while sparser layers contain redundant tokens.”
“However, discarding tokens permanently erases their information, which proves to be suboptimal for tasks such as retrieval”
Beaten on benchmarks
Head-to-head results where a newer method reports beating H2O. Values are copied from the source paper's tables — verify against the cited paper.
RLKV beats H2O
63.8 vs 0.6
accuracy_pct · [Llama-3.1-8B-R1 MBPP sparsity=0.4]
Which Heads Matter for Reasoning? RL-Guided KV Cache CompressionKVTC beats H2O
99.8 vs 16.2
LITM · [Mistral NeMo 12B]
KV Cache Transform Coding for Compact Storage in LLM InferenceVL-Cache beats H2O
120.11 vs 20.87
CIDEr · [Coco-Caption, LLaVA-1.6-34B, 5% cache budget]
VL-Cache: Sparsity and Modality-Aware KV Cache Compression for Vision-Language Model Inference AccelerationRefreshKV beats H2O
86 vs 21
Accuracy · [Llama-3.1-8B RULER]
RefreshKV: Updating Small KV Cache During Long-form GenerationA²ATS beats H2O
86.3 vs 22.3
Accuracy · [MegaBeam-Mistral-7B-512K, Sparsity ~0.062]
A$^2$ATS: Retrieval-Based KV Cache Reduction via Windowed Rotary Position Embedding and Query-Aware Vector QuantizationLOOK-M beats H2O
5.3 vs 1.4
NH · [LLaVA-v1.5-7B, α₁=0.1, α₂=0.1]
LOOK-M: Look-Once Optimization in KV Cache for Efficient Multimodal Long-Context InferenceEMS(w.o. pos) beats H2O
31.94 vs 8.47
Avg. · [LongChat-7B-v1.5-32k, cache budget 256]
EMS: Adaptive Evict-then-Merge Strategy for Head-wise KV Cache Compression Based on Global-Local ImportanceForesightKV beats H2O
43.3 vs 14.5
AIME2025 · [Qwen3-4B, 1K budget]
ForesightKV: Optimizing KV Cache Eviction for Reasoning Models by Learning Long-Term ContributionLouisKV beats H2O
19.39 vs 7.36
NarrativeQA · [Qwen2.5-7B-Instruct]
LouisKV: Efficient KV Cache Retrieval for Long Input-Output SequencesSnapKV beats H2O
41.38 vs 20.01
MF-en · [LWMChat model, 2048 cache size]
SnapKV: LLM Knows What You are Looking for Before GenerationH2O+CAOTE beats H2O
33.31 vs 16.89
Avg accuracy · [Llama 3.1-8B, 2k budget]
CAOTE: KV Cache Selection for LLMs via Attention Output Error-Based Token EvictionMeta-Soft beats H2O
75.72 vs 43.20
Avg · [All context lengths]
Meta-Soft: Leveraging Composable Meta-Tokens for Context-Preserving KV Cache Compression
What to use instead
Recent methods in the same sub-problem, not yet superseded in the knowledge base — arXiv benchmark leaders, not vetted production recommendations.
- STaR-KVSTaR-KV: Spatio-Temporal Adaptive Re-weighting for KV Cache Compression in GUI Vision-Language ModelsJun 1, 2026
- May 29, 2026
- May 28, 2026
- May 26, 2026
- May 25, 2026
- CONF-KVCONF-KV: Confidence-Aware KV Cache Eviction with Mixed-Precision Storage for Long-Horizon LLMMay 24, 2026
- May 21, 2026
- May 12, 2026
- Global Retention-Based KV EvictionMake Each Token Count: Towards Improving Long-Context Performance with KV Cache EvictionMay 10, 2026
- ReST-KVReST-KV: Robust KV Cache Eviction with Layer-wise Output Reconstruction and Spatial-Temporal SmoothingMay 9, 2026
- May 8, 2026