In this article
RRF combines rank positions, whereas DBSF normalizes the score distribution of the points returned for each query.
RRF and DBSF answer different fusion questions in Qdrant: one combines positions, while the other preserves information about score gaps. Choose between them with the same labeled queries and candidate pools, rather than treating either name as a universal relevance upgrade.
What each method retains
The hybrid-query reference describes RRF as rank-based fusion and DBSF as normalization of each returned score distribution before addition. DBSF uses statistics from that query’s returned points, not a permanently learned global calibration. Consequently, changing the returned population can change its normalization. RRF also depends on which documents reached its input lists, even though it does not compare their original score magnitudes.
Freeze the retrieval inputs first
Preserve the dense model revision, lexical configuration, filters and candidate depth for each branch. Qdrant’s fusion-selection guide separates this candidate-generation question from the final combination. Otherwise a wider sparse prefetch may recover a missing document and incorrectly receive credit as a better fusion algorithm. Export branch results before fusion so the experiment can explain where each final document originated.
Use a transparent toy fixture
The following ranks are illustrative, not measured results. They expose agreement and disagreement without inventing latency or accuracy figures.
| Document | Dense rank | Sparse rank |
|---|---|---|
| A | 1 | 3 |
| B | 2 | 1 |
| C | 3 | Absent |
| D | Absent | 2 |
Save original scores alongside these positions for the DBSF trial. A rank-only table cannot reconstruct score gaps. Also preserve the handling of documents absent from one branch; absence is not an original relevance score of zero.
Compare by query class
Use a held-out set containing exact identifiers, paraphrased questions and queries whose answer appears in several documents. Judge the final evidence, not only agreement between the methods. A fusion setting can help identifier queries while reducing useful semantic results. Keep document grouping unchanged as well: the multi-representation example shows grouping and prefetch as additional operations that can alter what a user receives.
Diagnose an unexpected winner
When DBSF changes sharply after increasing candidate depth, inspect the distribution of the newly included scores. When RRF produces surprising ties, inspect branch ranks and overlap before changing weights. Do not normalize a quantity already transformed elsewhere without documenting both stages. Preserve query-specific explanations, since an average relevance metric alone cannot distinguish missing candidates from an unsuitable combination of candidates already present.
Keep a reversible decision record
Record branch settings, fusion method, evaluation queries and the source documents used for judgments. Compare the methods under the same output count and filters, then repeat only the affected queries after a deliberate change. The useful outcome is a supported choice for a corpus and request mix. It is not evidence that one method always wins, nor permission to reuse a tuned setting after replacing the embedding model or lexical analyzer.
Related reading: Qdrant for RAG: deciding what belongs in RAM or on disk; A GPU inference benchmark you can trust.