is [ BM25 + vector ]+ RRF really worth it?
Summary
This post questions whether combining BM25 and vector search with RRF improves hit rates in agentic memory retrieval, suggesting BM25 alone may suffice.
Similar Articles
@DailyDoseOfDS_: Stop using vector search everywhere! A 30-year-old algorithm with zero training, zero embeddings, and zero fine-tuning …
The article argues against overusing vector search, highlighting BM25's effectiveness for exact keyword matching and its role in hybrid search systems.
@Al_Grigor: Don't start a RAG project with vector search by default. Start with a text search. It is simpler: - No embedding model …
A practical advice thread recommending to start RAG projects with text search (BM25) instead of defaulting to vector search, to reduce complexity; vector search should be added only when semantic gaps become apparent.
RAG Retrieval Deep Dive: BM25, Embeddings, and the Power of Agentic Search
This article provides an in-depth comparison of the advantages and disadvantages of BM25 lexical search and embedding semantic search in RAG retrieval, offers a practical framework for selecting retrieval methods based on query type and system trade-offs, and emphasizes the importance of treating RAG as a system rather than a simple component.
When More Documents Hurt RAG: Mitigating Vector Search Dilution with Domain-Scoped, Model-Agnostic Retrieval
This paper identifies 'vector search dilution' in RAG systems when scaling to large, heterogeneous document collections, and proposes MASDR-RAG, a domain-scoped retrieval approach that significantly improves retrieval accuracy by leveraging organizational metadata.
Introducing Contextual Retrieval
Anthropic introduces Contextual Retrieval, a technique combining contextual embeddings and BM25 to significantly improve RAG accuracy by reducing failed retrievals.