Why Memory Evaluation Matters

Most AI agent memory systems retrieve information by maximizing context window size. That works on benchmarks but not in production, where every token adds cost. Token efficiency — achieving high accuracy with less context per query — is what separates benchmark performance from production viability.

The new Mem0 algorithm achieves competitive accuracy on LoCoMo, LongMemEval, and BEAM while averaging under 7,000 tokens per retrieval call. Full-context approaches on the same benchmarks routinely consume 25,000+ tokens per query.

Evaluating a memory system at scale comes down to three parameters: accuracy (what the benchmarks measure), cost (context tokens per query), and performance (latency). Optimizing one is easy. Balancing all three at scale is the actual problem.

Some benchmarks today — particularly smaller ones like LoCoMo and LongMemEval — can be materially improved by aggressive retrieval strategies, larger context windows, or frontier models. That does not necessarily mean the underlying memory system has gotten better. We evaluate under constraints that reflect how memory systems actually run in production: limited context windows and practical token budgets.

Architecture Overview

Mem0's memory system operates across two phases — extraction (writing) and retrieval (reading) — with an entity linking layer connecting them.

Memory Extraction (Distillation)

When new conversations arrive, the extraction pipeline processes them through five stages:

1. Store New Memories — Conversation enters the pipeline asynchronously (after the agent responds)
2. Context Lookup — Find related existing memories to avoid duplicates
3. Distill Memories — Single-pass LLM extraction produces ADD-only facts from input + context
4. Deduplicate + Embed — Hash-based deduplication, then vectorize new memories
5. Entity Linking — Identify entities (proper nouns, quoted text, compound noun phrases) and link them across memories

Memories are distributed across three storage layers, each tuned for a specific retrieval pattern:

Multi-Signal Retrieval

When a query arrives, the retrieval pipeline scores candidates across three signals in parallel:

1. Semantic Search — Vector similarity scoring against memory embeddings
2. Keyword Search — Normalized term matching via BM25 with verb-form lemmatization
3. Entity Search — Entity graph matching boosts memories linked to query entities

Results are fused via rank scoring into a final top-K set. Different query types lean on different signals:

The combined score outperformed every individual signal across every category tested.

Benchmarks

LoCoMo

LoCoMo tests single-hop, multi-hop, open-domain, and temporal memory recall across conversational sessions.

Mean tokens: 6,956

The two largest gains are temporal queries (+29.6) and multi-hop reasoning (+23.1). Both categories directly test the ADD-only architecture (preserving temporal context) and entity linking (connecting facts across memories).

LongMemEval

LongMemEval evaluates memory across single-session and multi-session contexts, including knowledge updates and temporal reasoning.

Mean tokens: 6,787

The biggest gain is single-session assistant (+53.6) — the previous algorithm had a blind spot for agent-generated facts. The new algorithm treats them as first-class memories.

The +42.1 on temporal reasoning reflects the ADD-only architecture preserving chronological context that the previous UPDATE/DELETE model would destroy.

BEAM

BEAM evaluates memory systems at 1M and 10M token scales across ten task categories. It is the only public benchmark that operates at context volumes production AI agents actually encounter.

Mean tokens (1M): 6,719. Mean tokens (10M): 6,914.

Performance Summary

All results use a single-pass retrieval setup: one retrieval call, one answer, no agentic loops.

All benchmarks run on the same production-representative model stack. Scores carry a ±1 point confidence interval due to judge inconsistency.

Running Evaluations

The full evaluation framework is open-sourced so anyone can reproduce the numbers independently. It supports both Mem0 Cloud and self-hosted OSS backends.

Setup

# Set your API keys
export MEM0_API_KEY=m0-your-key
export OPENAI_API_KEY=sk-your-key
```

# Copy and configure environment
cp .env.example .env
# Edit .env to add OPENAI_API_KEY

# Start local Mem0 server + Qdrant
docker compose up -d
# Mem0 server: http://localhost:8888
# Qdrant:      http://localhost:6333
```

Running a Benchmark

Each benchmark is a Python module with its own runner (source code). All share common CLI options:

Self-hosted

python -m benchmarks.locomo.run
--project-name my-eval
--top-k 200

```bash LongMemEval
# 500 questions across 6 categories
python -m benchmarks.longmemeval.run \
  --project-name my-eval \
  --backend cloud \
  --mem0-api-key $MEM0_API_KEY \
  --all-questions \
  --top-k 200

# Self-hosted
python -m benchmarks.longmemeval.run \
  --project-name my-eval \
  --all-questions \
  --top-k 200

# 1M token scale (100 conversations)
python -m benchmarks.beam.run \
  --project-name my-eval \
  --backend cloud \
  --mem0-api-key $MEM0_API_KEY \
  --chat-sizes 1M \
  --conversations 0-99 \
  --top-k 200

# 10M token scale
python -m benchmarks.beam.run \
  --project-name my-eval \
  --backend cloud \
  --mem0-api-key $MEM0_API_KEY \
  --chat-sizes 10M \
  --conversations 0-99 \
  --top-k 200

Custom Model Configuration

To run evaluations with custom models (Azure OpenAI, Ollama, etc.), copy one of the provided configs:

# Available configs: openai.yaml, azure-openai.yaml, ollama.yaml
cp configs/azure-openai.yaml mem0-config.yaml
# Edit mem0-config.yaml with your model details

# Uncomment the volume mount in docker-compose.yml, then restart:
docker compose down && docker compose up -d

Viewing Results

Results are saved to results/[benchmark]/ and can be explored through the built-in web UI:

npm install
npm run dev -- -p 3001
# Open http://localhost:3001

The UI lets you browse per-question results, inspect retrieval details, and compare multiple runs.

Result Format

Each evaluated question produces a structured result:

{
  "id": "locomo_q_001",
  "group": "temporal",
  "question": "When did the user first mention moving?",
  "ground_truth": "During the March 3rd conversation",
  "retrieval": {
    "search_query": "when did user mention moving",
    "search_results": ["..."],
    "search_latency_ms": 123.4,
    "total_results": 42
  },
  "generation": {
    "generated_answer": "The user first mentioned moving on March 3rd",
    "model": "<answerer-model>",
    "prompt_tokens": 500,
    "completion_tokens": 100
  },
  "judgment": {
    "judgment": "CORRECT",
    "score": 0.85,
    "reason": "Answer correctly identifies the date",
    "model": "<judge-model>"
  },
  "cutoff_results": {
    "top_10": { "score": 0.75, "judgment": "CORRECT" },
    "top_50": { "score": 0.85, "judgment": "CORRECT" },
    "top_200": { "score": 0.90, "judgment": "CORRECT" }
  }
}

Interpreting Results

When evaluating memory systems, keep these considerations in mind:

• Saturating a small benchmark is not the same as building a memory system that works at scale. Small benchmarks can be brute-forced with aggressive retrieval and frontier models.
• Token efficiency matters as much as accuracy. A system that scores 95% using 25K tokens per query isn't comparable to one scoring 90% using 7K tokens. Report mean tokens per query alongside scores.
• Compare at equal constraints. Always compare systems using the same retrieval budget, the same model, and the same latency budget. A frontier model at maximum recall is not comparable to a smaller production-grade model at production-realistic retrieval depth.
• Watch for score ceiling effects. Categories like "single-session user" are already near-saturated (97%+). Improvements in these categories are less meaningful than gains in harder categories like temporal reasoning or multi-session.
• BEAM at 10M is the real test. Any system can look good at small scale. The 10M-token BEAM benchmark reveals whether the retrieval system actually scales.

FAQ

Resources