Same system, very different scores depending on the judge. How do you read memory benchmarks?
Summary
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.
Similar Articles
What would a memory benchmark have to do before you'd trust the number?
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.
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.
Ask Which, Not How Good: Sizing Benchmarks Scored by an LLM
This paper investigates the measurement limitations of LLM-judged benchmarks, showing that generalizability is constrained by judge variability and that protocol design significantly affects performance ceilings, with implications for AI benchmarking methodologies.
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.
The Two MMLU Scores: What a Benchmark Name Does Not Fix (23 minute read)
The article examines the issues with MMLU benchmark scores, showing that different model builds can yield incomparable accuracies due to open evaluation variables, and proposes a content-addressed framework for better traceability.