Fetching from the wire…
Public story · 2026-07-30 · high
The gains come from skipping re-prefill entirely, but accuracy dips to 60.3% versus Mem0's 63.3%.
Why now: Covered in the July 30 briefing on agent-infrastructure research.
InferScale precomputes retrieved memory facts as cached GPU keys and injects them straight into vLLM's paged attention cache, per the arXiv paper. That replaces the re-prefill step most memory-augmented agents run on every single call.
Mem0, MemGPT, and Zep all re-run that prefill step on every call, the exact tax the paper targets. Across three open-weight models on the LoCoMo benchmark, InferScale cut time-to-first-token 72-79% and pushed throughput up 3.7-4.5x under concurrent load.
The trick is in how it handles position. Chunked RoPE stores each fact's keys before rotation gets applied, so a cached fact slots into any position in a new prompt. Context-Window Encoding then recovers the cross-fact context that normally gets lost when facts are cached in isolation, the paper says.
It runs through vLLM's existing KV-connector interface, so it needs no changes to the inference engine and no fine-tuning of the underlying model.
InferScale scored 60.3% accuracy on LoCoMo against Mem0's 63.3%, and the paper doesn't say how that gap moves at higher retrieval depths.
Most agents don't need the last few points of recall precision. They need to stop stalling on every turn. What's worth watching is whether anyone closes that accuracy gap without giving back the speed.
Each link below shares sources, entities, or timing with this story.
Memori benchmarked against mem0 / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Memori benchmarked against mem0); both cover Context, LoCoMo, Mem0; overlapping topics (accuracy, agent, context, mem0, memory).
mem0 benchmarked against LoCoMo / Shared entities / Earlier coverage / Tension
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo, Mem0, MemGPT; earlier LoCoMo coverage from 2026-07-28.
mem0 benchmarked against LoCoMo / Shared entity: LoCoMo / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; reported by the same outlet (arxiv.org).
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; reported by the same outlet (arxiv.org).
mem0 benchmarked against LoCoMo / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo, Mem0; overlapping topics (agent, fact, memory).
mem0 benchmarked against LoCoMo / Shared entity: LoCoMo / Earlier coverage
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; earlier LoCoMo coverage from 2026-07-21.
mem0 benchmarked against LoCoMo / Shared entity: LoCoMo / Shared topic / Earlier coverage
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; overlapping topics (agent, memory).
mem0 benchmarked against LoCoMo / Shared entity: LoCoMo / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (mem0 benchmarked against LoCoMo); both cover LoCoMo; reported by the same outlet (arxiv.org).