Research complete: both score-based and RRF merge fail 0.95 threshold. Updated research doc with full RRF validation results and confidence intervals. Added benchmark result reports and helper tests. Follow-up bead miroir-n6v created for global-IDF preflight (dfs_query_then_fetch pattern). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
10 KiB
Score Normalization at Scale — Statistical Validation of Cross-Shard Comparability
Bead: miroir-zc2.4 (validation: miroir-zfo) Date: 2026-04-18 (RRF validation: 2026-04-19) Status: ✗ FAIL — RRF insufficient, global-IDF preflight required
Executive Summary
Cross-shard score comparability is a significant concern for Miroir. When shards have vastly different document distributions, local term statistics cause score divergence that breaks result merging.
Score-based merge finding: Average Kendall tau of 0.79 vs. ground truth — well below the 0.95 pass threshold. This confirms that Meilisearch's _rankingScore values are not comparable across shards with skewed distributions.
RRF merge finding (2026-04-19): Average Kendall tau of 0.14 — catastrophically worse than score-based merge. RRF amplifies the bias from tiny shards because it assigns equal weight to rank-1 results regardless of shard size.
Recommendation: Global-IDF preflight (Elasticsearch dfs_query_then_fetch pattern) is required. RRF alone does not solve the comparability problem.
Problem Statement
Miroir's design assumes _rankingScore is comparable across shards. This holds when:
- All shards have identical index settings (addressed by §13.5 settings broadcast)
- All shards use the same term statistics for scoring
The second assumption fails when shards have different document counts. Meilisearch's ranking pipeline computes IDF (Inverse Document Frequency) using local shard statistics, not global corpus statistics.
The IDF Problem
IDF is computed per shard:
IDF(term) = log((N - df + 0.5) / (df + 0.5))
Where:
N= total documents in the shard (not global corpus)df= documents containing the term in the shard
When shards have very different sizes:
- Large shard (93K docs): common terms have high N, moderate IDF
- Small shard (10 docs): same terms appear rare relative to N, inflated IDF
This causes documents from small shards to receive artificially high scores.
Experimental Design
Corpus
- 100,000 documents total
- 10 shards with intentional skew:
- Shard 0: 930 docs (1× baseline)
- Shard 1: 93,015 docs (100× baseline — extreme outlier)
- Shard 2-7: ~930 docs each (baseline)
- Shard 8: 465 docs (0.5×)
- Shard 9: 10 docs (0.01× — tiny shard)
- 50 unique terms distributed following Zipf's law
- 5 categories: tech, finance, science, health, business
Queries
10,000 random queries across 5 types:
- Single-term (2,500): Basic term search
- Multi-term (2,500): Phrase-like queries
- Filtered (2,000): Category-filtered search
- Rare-term (1,500): Low document frequency terms
- Common-term (1,500): High document frequency terms
Metrics
- Kendall tau (τ): Ordinal correlation between rankings
- τ = 1.0: perfect agreement
- τ = 0.0: independent rankings
- τ = -1.0: perfect disagreement
- Pass criterion: Average τ ≥ 0.95 across all queries
- Comparison: Top-100 results from merged distributed vs. single-index ground truth
Simulation
Used a simplified BM25 scoring model to demonstrate the theoretical issue:
- Global IDF for ground truth (single-index)
- Local IDF per shard for distributed
- Merge by global score sort (current Miroir design)
Results
Overall
| Metric | Value |
|---|---|
| Total queries | 10,000 |
| Average Kendall tau | 0.7939 |
| Min tau | -1.0 |
| Max tau | 1.0 |
| Queries with τ < 0.95 | 6,306 (63.1%) |
| Queries with τ < 0.90 | 2,530 (25.3%) |
| Pass criteria (≥ 0.95) | ✗ FAIL |
By Query Type
| Query Type | Avg τ | Min τ | Max τ | Notes |
|---|---|---|---|---|
| Common-term | 0.1483 | 0.0 | 0.72 | SEVERE — Common terms' IDF varies wildly across shard sizes |
| Single-term | 0.8677 | 0.0 | 1.0 | Moderately affected |
| Filtered | 0.8719 | -1.0 | 1.0 | Moderately affected |
| Rare-term | 0.9387 | 0.92 | 0.96 | Best — rare terms have stable IDF |
| Multi-term | 0.9584 | -0.12 | 1.0 | Good — multiple terms average out variance |
Interpretation
The common-term result (τ = 0.15) is catastrophic. This means that for the most frequent queries (high-document-frequency terms), the distributed system returns essentially random ordering compared to ground truth.
The rare-term result (τ = 0.94) is better but still below threshold. Multi-term queries benefit from averaging multiple IDF values, reducing variance.
Root Cause Analysis
Why Common Terms Fail
Consider a term appearing in 50% of documents:
- Global corpus (100K docs): df ≈ 50,000 → IDF ≈ 0.69
- Large shard (93K docs): df ≈ 46,500 → IDF ≈ 0.69 ✓
- Tiny shard (10 docs): df ≈ 5 → IDF ≈ 1.38 ✗
Documents in the tiny shard receive 2× higher scores for the same term, dominating the merged results despite potentially being less relevant globally.
Why This Matters
This is not theoretical — it directly impacts relevance:
- Tiny shards dominate: Documents from small shards appear at the top
- Relevance is inverted: Less relevant globally-relevant docs are outranked
- Skew accelerates: As shards become unbalanced (node churn, migration), the problem worsens
Recommendations
Option 1: Global Statistics Preflight (ES dfs_query_then_fetch pattern)
Add a pre-query round-trip to gather global term statistics:
- Query all shards for term frequencies
- Compute global IDF at coordinator
- Send global IDF with query phase
- Shards use global IDF for scoring
Pros: Correct scores, ES-proven pattern Cons: +1 round-trip latency, increases per-query overhead
Option 2: Reciprocal Rank Fusion (RRF) — VALIDATED, INSUFFICIENT
Abandon score-based merging entirely. Use rank-based fusion:
RRF(doc) = Σ (1 / (k + rank_shard(doc)))
where k = 60 (default).
Validation result (2026-04-19): RRF merge produces τ = 0.14 against ground truth — catastrophically worse than score merge (τ = 0.79). Root cause: RRF assigns equal weight to the #1 result from a 10-doc shard and the #1 result from a 93K-doc shard. With extreme skew, top-ranked documents from tiny shards (which have inflated local IDF) receive disproportionate RRF scores.
Pros: Immune to score scale differences, no preflight, simple Cons: Fails catastrophically with shard size skew; ignores score magnitudes entirely
Option 3: Score Normalization by Shard Size
Apply a normalization factor based on relative shard sizes:
normalized_score = raw_score × (N_shard / N_global)^α
where α is tuned empirically.
Pros: No preflight, correct-ish scores Cons: Heuristic, requires tuning, still an approximation
Recommendation
Option 1 (global-IDF preflight) is now required. RRF validation showed it degrades rather than improves ranking quality under extreme shard skew. The dfs_query_then_fetch pattern is the proven solution used by Elasticsearch.
RRF remains useful as a secondary merge strategy for hybrid search (combining vector and keyword results) where cross-shard scoring is not the issue.
Follow-Up Work
Status: RRF validation (miroir-zfo) confirmed RRF is insufficient for cross-shard comparability.
RRF Validation Results (2026-04-19, bead miroir-zfo)
Full 10K-query benchmark comparing RRF merge against single-index ground truth:
| Metric | Score Merge | RRF Merge |
|---|---|---|
| Avg Kendall τ | 0.7939 | 0.1369 |
| 95% CI | [0.7873, 0.8006] | [0.1339, 0.1399] |
| Min τ | -1.0 | -0.2105 |
| Queries with τ < 0.95 | 6,306 (63.1%) | 9,998 (100.0%) |
| Pass (≥ 0.95) | ✗ FAIL | ✗ CATASTROPHIC |
Per-type RRF results:
| Query Type | Score τ | RRF τ | Δ |
|---|---|---|---|
| Common-term | 0.1483 | 0.1101 | -0.04 |
| Single-term | 0.8677 | 0.1506 | -0.72 |
| Filtered | 0.8719 | 0.0985 | -0.77 |
| Rare-term | 0.9387 | 0.2360 | -0.70 |
| Multi-term | 0.9584 | 0.1105 | -0.85 |
Root cause: RRF assigns 1/(k + rank) per shard regardless of shard size. In skewed distributions:
- #1 result from 10-doc shard: RRF = 1/61 = 0.0164
- #1 result from 93K-doc shard: RRF = 1/61 = 0.0164 (identical!)
- But the 93K-doc shard's #1 result is globally far more relevant
This equal-weight property (a strength in balanced scenarios) becomes a catastrophic liability with shard size skew.
Action required: Implement global-IDF preflight (Option 1). A bead should be created for this work.
Confidence Intervals
The experiment used 10,000 queries, providing narrow confidence intervals:
Score-based merge
| Query Type | Avg τ | 95% CI | n |
|---|---|---|---|
| Overall | 0.7939 | [0.7873, 0.8006] | 10,000 |
| Common-term | 0.1483 | [0.1336, 0.1630] | 1,500 |
| Single-term | 0.8677 | [0.8583, 0.8771] | 2,500 |
| Filtered | 0.8719 | [0.8614, 0.8824] | 2,000 |
| Rare-term | 0.9387 | [0.9378, 0.9395] | 1,500 |
| Multi-term | 0.9584 | [0.9564, 0.9603] | 2,500 |
RRF merge (validated 2026-04-19)
| Query Type | Avg τ | 95% CI | n |
|---|---|---|---|
| Overall | 0.1369 | [0.1339, 0.1399] | 10,000 |
| Common-term | 0.1101 | [0.1013, 0.1189] | 1,500 |
| Single-term | 0.1506 | [0.1447, 0.1564] | 2,500 |
| Filtered | 0.0985 | [0.0927, 0.1043] | 2,000 |
| Rare-term | 0.2360 | [0.2292, 0.2428] | 1,500 |
| Multi-term | 0.1105 | [0.1046, 0.1164] | 2,500 |
Artifacts
Benchmark infrastructure: tests/benches/score-comparability/
corpus/generate.py— Synthetic corpus generator with shard skewqueries/generate.py— Random query set generatorsimulate.py— BM25-based score simulationresults/compare.py— Kendall tau comparison toolresults/comparison-report-score.json— Score merge vs ground truthresults/comparison-report-rrf.json— RRF merge vs ground truth
Rerun: cd tests/benches/score-comparability && python3 simulate.py