Beyond Benchmarks: Evaluating Embedding Model Similarity for RAG Systems (arXiv, July 2024)
- Authors: Laura Caspari, Kanishka Ghosh Dastidar, Saber Zerhoudi, Jelena Mitrovic, Michael Granitzer
- Source: https://arxiv.org/abs/2407.08275
- Type: Academic paper — Embedding models
- Benchmark scores alone may hide substantial behavioral differences between embedding models; two models with close nDCG@10 can retrieve noticeably different document sets.
- Embedding-model similarity analysis can inform whether retrieval results from one model can substitute or complement another in a RAG stack.
- The work situates itself in the modern retrieval stack: dense bi-encoders, cross-encoder rerankers, late-interaction models, and LLM-centric agentic retrieval.
- Datasets: BEIR, MS MARCO, Natural Questions, domain-specific corpora
- Metrics: nDCG@10, MRR, Recall@k, Hit@k, task success rate
- Baselines: BM25, dense retrieval, cross-encoder rerankers, retrieval-free LLMs
- BGE M3-Embedding (arXiv:2402.03216)
- Arctic-Embed 2.0: Multilingual Retrieval Without Compromise (arXiv:2412.04506)
- BGE-en-ICL / BGE-ICL few-shot embedders (arXiv:2409.15700)
Overview
The paper argues that standard benchmark leaderboards are insufficient for choosing embedding models for Retrieval-Augmented Generation (RAG). Instead of only comparing models by aggregate retrieval metrics, it analyzes the similarity between embedding models themselves — i.e., whether different models retrieve the same or different documents — and what this means for model selection, result transferability, and the reliability of benchmark-based conclusions in RAG pipelines.
Key Points
Positioning in the Field
Neural IR has evolved from BM25 to dense retrieval, cross-encoder reranking, and now generative/agentic search where the LLM decides *whether and how often* to retrieve. In this landscape, RAG evaluation is shifting from static nDCG toward task success, citation accuracy, and multi-hop reasoning quality — making embedding model behavior, not just its leaderboard score, a critical variable.
Practical Takeaways for Engineers
| Concern | Recommendation | |---------|----------------| | Latency | Cascaded retrieval + early stopping, cache hot queries | | Quality | Verify offline gains transfer to online CTR/satisfaction via interleaving tests | | Data safety | PII partitioning, versioned embeddings, rollback capability | | Security | Source whitelisting, poisoning detection, output filtering | | Cost | Hybrid sparse+dense retrieval, model routing/distillation |