Agent BenchmarkVerified 36 days ago
Long-Context RAG Recall Benchmark
New benchmark measuring how well agents and models retrieve facts from very long documents. Long-context models are closing the gap with vector RAG on many tasks.
Claude 4 Opus, Gemini 2.5 Pro, GPT-5.2, Qwen3.6-27BClaude 4 Opus / Gemini 2.5 Pro / GPT-5.22026-06-24
Winner:Gemini 2.5 Pro
Results dashboard
Overall score
Gemini 2.5 Pro
92
Claude 4 Opus
89
GPT-5.2
87
Qwen3.6-27B
84
Results table
| Agent | Score | Time | Cost | Pass |
|---|---|---|---|---|
| Gemini 2.5 Pro | 92 | — | — | Fail |
| Claude 4 Opus | 89 | — | — | Fail |
| GPT-5.2 | 87 | — | — | Fail |
| Qwen3.6-27B | 84 | — | — | Fail |
The task
This benchmark measures how well an agent or model retrieves specific facts from long documents without external retrieval augmentation. Documents range from 32K to 1M tokens and include legal contracts, technical manuals, research papers, financial reports, and synthetic needle-in-haystack tests.
Two approaches are compared:
- Long-context stuffing: pass the entire document to the model and ask questions.
- Vector RAG: chunk the document, embed it, and retrieve the top-k chunks before generation.
The benchmark reports recall accuracy, latency, and cost for each approach.
Scoring rubric
| Criterion | Weight | Notes |
|---|---|---|
| Recall accuracy | Primary | Percentage of questions answered correctly using only the provided document. |
| Multi-hop recall | Secondary | Questions requiring combining facts from two or more distant sections. |
| Needle-in-haystack | Reported | Single fact placed at varying depths in long contexts. |
| Cost per 1M tokens | Reported | Normalized cost for fair comparison. |
Key findings
- Frontier long-context models are competitive with RAG. On documents under 256K, top models match or beat a naive vector-RAG baseline.
- RAG still wins on very large corpora. When the corpus exceeds 1M tokens, retrieval plus a smaller model is cheaper and often more accurate.
- Multi-hop reasoning favors long context. Connecting facts across distant sections is harder when chunks are retrieved independently.
- Cost favors RAG at scale. Long-context frontier models can cost 10–50x more per query than retrieval over embeddings.
- Open-weight models are catching up. Qwen3.6-27B scores within single-digit points of top proprietary models on 128K–256K tasks.
Honest caveats
- Synthetic needle tests do not fully represent real retrieval work.
- Chunking strategy and embedding quality strongly affect RAG scores.
- Models with larger advertised context windows do not always use them effectively.
- Latency and cost are provider-dependent and change frequently.
When to use this benchmark
- For architects: Decide between long-context stuffing and RAG based on document size and question complexity.
- For buyers: Compare model claims against measured recall, not just context-window size.
- For researchers: Test new retrieval techniques against a reproducible long-context baseline.
Source
- Long-context RAG recall benchmark leaderboard and dataset: results compiled from public model evaluations and provider benchmarks as of 2026-06-24.