Repository navigation
perf: tune automatic probing for small centroid routers - #132
Merged
JingsongLi merged 1 commit intoNov 19, 2026
Merged
Conversation
|
Benchmark run · success · attempt 1 Vector index benchmark🟢 No alerts (5/5 indexes)
🟡 QPS ↓ >10% or Recall ↓ >1pp · 🔴 QPS ↓ >20% or Recall ↓ >3pp. Advisory only; QPS is measured after warmup. Absolute metrics & environmentMedians, base → PR. QPS is timed after warmup; P95 uses the first warm sweep.
Base |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Use an automatic outer probe floor of 3 for a four-centroid router and 4 for an eight-centroid router. The floor enters the existing candidate-count and filter-selectivity calculation before expansion and clamping. The caller can still set an explicit probe width. The ordinary IVF reader keeps its existing floor of 8.
The behavior is shared by IVF and DiskANN shard layouts through the existing
CentroidRouter.resolveNprobeAPI. The serialized model and JNI signatures are unchanged. Paimon integration and benchmarkVerification
Rust workspace tests, Clippy with warnings as errors, rustfmt and the Java API suite passed. Regression tests exercise 4 and 8 centroids, adjacent counts, large top-K, filtered searches, fixed probes and the ordinary IVF policy.
Compared two release JNI builds against the same pinned index snapshot for each pair. The baseline was
e794291. The Paimon benchmark omitscentroid.nprobein both arms. The dataset contains 100,000 SIFT vectors (L2, 128 dimensions) in four disjoint row-ID ranges. Random masks retain exactly 80%, 50% or 5% of rows per range. Ground truth is exhaustive L2 within the eligible set. Each pair used the same 80–512 held-out queries and identical shard-local settings. Inputs came from original SIFT query positions 8000–9249. Fresh readers counted all logical bytes returned by Paimon streams, including the routers, on an Apple M4 Pro with four native threads.All 32 paired scenarios met the existing recall criterion, an absolute mean difference of at most 1 percentage point and a paired 95% bootstrap lower bound above −1 point. The largest measured recall decrease was 0.111 points (IVF-FLAT, 8 centers, K=1000, 100% eligible). The lowest lower bound was -0.180 points. 10,944 paired query measurements were taken across scenarios. Scenarios can reuse query IDs. The table gives old → new.