mlsanityData to 7 Oct 2026

Positions Are Not Facts: The Mismatch Between KV Caches and Memory

arXiv 2609.33759 ↗First posted 27 Sep 2026cs.CL cs.LGcited by 0

On the map: Efficient LLM inference and serving → KV cache optimization

Abstract (arXiv)

When a fact changes, how should a language model update the history stored in its key-value (KV) cache? Hiding the old record is cheap, but it may still contain needed details or answer questions about the past. We compare hiding whole records, hiding only replaced values, and deleting old text and recomputing the cache. In a controlled quantity task, masking makes all eight models prefer the new value more strongly, yet six lose complete answers through unit errors or failure to stop; keeping the unit preserves all current answers. Later states also retain useful information from earlier records: on multi-hop updates, rebuilding these states at unchanged positions lowers historical accuracy by 20-41 percentage points, whereas moving the existing states has little effect. Keeping object dependencies and unchanged revision passages prevents many losses. Recognition is a separate challenge. Learned readouts recover distinctions missed by fixed cache similarities on synthetic record pairs. On natural text, text-detector-selected masks show no clear advantage over random masks at the same rate in 14 same-model detector-generator comparisons. Query-dependent access can avoid some losses, with additional storage or access costs. These findings identify what must be preserved beyond the replaced value when using a KV cache as updatable memory.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in KV cache optimization, one of 12 directions in Efficient LLM inference and serving. First posted on arXiv 27 Sep 2026.

Builds on

0 of 0 references.

No references here yet.

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Correct Now, Insufficient Later: Auditing Update Sufficiency in Context Compression
  2. 2026Contiguity, Not Importance: Budgeted Repair of Stale KV Caches After Document Edits
  3. 2026Rethinking KV Cache Eviction via a Unified Information-Theoretic Objective
  4. 2026Small Frequency Corrections Can Change What Survives KV Cache Compression
  5. 2025Whose Narrative is it Anyway? A KV Cache Manipulation Attack
  6. 2026Does Your Agent's Memory Survive a Model Upgrade? A Controlled Study of Memory Portability
  7. 2026Back from the Future: Key-Value Cache Management by Counter-Causal Surprise
  8. 2026What Should an Agent Forget? Separating What Is Stored from What Is Used