Rank fusion versus score fusion
Reciprocal Rank Fusion, or RRF, combines results primarily from their ranks. A candidate receives a contribution based on its position in each result list, so the absolute score values do not need to be comparable across retrieval systems.
Distribution-Based Score Fusion, or DBSF, instead uses the score distributions of the result sets to normalize their scores before combining them. That allows score magnitude to contribute, but it also means the result distribution can influence the final ranking.
The trade-off is robustness versus score information. RRF is attractive when dense and sparse systems produce incompatible score scales or when you want a simple rank-based ensemble. DBSF can be useful when relative score distributions contain meaningful information and the result sets have enough statistical stability.
A common mistake is treating a larger raw score as inherently comparable across prefetches. Dense cosine scores, sparse scores, and other ranking functions can have very different scales. Fusion should explicitly account for that. Exact fusion behavior and parameter details should be checked against the Qdrant version in use.
RRF is based on result rank and does not require comparable raw scores
DBSF uses normalized score distributions
RRF is often robust for heterogeneous retrieval signals
Fusion choice should be evaluated on representative relevance data
Dense and sparse searches return scores on completely different scales. Why is simply adding the raw scores unsafe?
What information does RRF use if it does not rely on comparable raw score magnitudes?
Your RRF results are stable across queries but DBSF performs better on a well-labeled dataset. What would you investigate before choosing DBSF?
A sparse retriever suddenly changes its score distribution after a model upgrade. Which fusion strategy would you expect to be more sensitive to that change?
Your dense retriever returns tightly clustered scores while the sparse retriever has a wide score range. How would that affect your evaluation of RRF versus DBSF?
You need to combine three retrieval systems with different score semantics. How would you design an experiment to select the fusion strategy?
A global search platform uses multiple retrievers whose score distributions drift over time. How would you choose and monitor a fusion strategy that remains robust?
Offline evaluation shows DBSF wins on average but occasionally produces severe ranking regressions for certain query classes. How would you decide whether to use RRF, DBSF, or a query-dependent strategy?