What would a memory benchmark have to do before you'd trust the number?
Summary
The author critiques the reliability of memory benchmarks for LLMs, citing issues like incorrect golden answers in LoCoMo and inconsistent scoring metrics yielding large score gaps. They question whether practitioners trust these numbers and discuss recent improvements like LongMemEval's knowledge update questions.
Similar Articles
Same system, very different scores depending on the judge. How do you read memory benchmarks?
A discussion on how unreliable LLM memory benchmarks can be, noting that scores swing wildly depending on the evaluator model (e.g., 51.4 under token-overlap F1 vs. 75.8 under an LLM judge), the reader model, and run counts — while many results are vendor-reported with unclear noise levels.
anyone else notice memory API benchmark numbers are all over the place?
The post questions the reliability of benchmark scores for memory APIs like Mem0 and Zep, noting significant discrepancies between self-reported and third-party numbers on the LoCoMo benchmark, suggesting these metrics may be more marketing than accurate comparisons.
Same retrieval, different answers: 32 of 500 LongMemEval results flipped
This article highlights that benchmark scores for Engrava, a memory layer tool, can vary due to reader or judge stage variance even when retrieval results are unchanged, using LongMemEval results to illustrate the issue.
Honest question: would you run this long-term memory benchmark on your own system?
A company building memory infrastructure introduces 'glasshouse', a draft long-term memory benchmark with 2,847 questions over a 1.97M token conversation in 10 languages, reporting 17 separate axes (including fact-update consistency and conflict resolution) without a single headline score, and asks the agent-memory community for feedback.
MemTrapBench: Benchmarking Cognitive Traps in LLM Memory Use
This paper introduces MemTrapBench, a benchmark for evaluating cognitive traps in LLM memory use, and proposes AdaptiveMem, an inference-time method to mitigate these traps while preserving performance on standard benchmarks.