perf(fts): enable the bulk MAXSCORE path by default#7604
Draft
BubbleCal wants to merge 1 commit into
Draft
Conversation
This was referenced Jul 3, 2026
With right-sized partitions the bulk path reaches Lucene-parity latency (k10 0.034-0.037s/213-235qps vs Lucene 10.4's 0.037s/216qps on the same 200M-doc corpus, queries, and warm protocol) and its results are score-identical to the classic WAND loop. LANCE_FTS_MAXSCORE=0 opts back into the classic loop.
4732787 to
fec0a88
Compare
0781681 to
acac9d8
Compare
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.
Stacked on the bulk MAXSCORE PR; flips the default.
Verification vs #7603 (its base)
Per-branch-tip wheels on the 200M-doc v3-256 index (1000 3-word OR queries
× 8 concurrent, warm): default-on reproduces #7603's opt-in numbers exactly
— k10 0.0342s vs 0.0342s, k100 0.0628s vs 0.0629s — i.e. the 3× win over
the classic loop now applies by default at both operating points. AND
queries are untouched (k10 0.113s vs #7602's 0.115s, within noise).
Results are score-identical to the classic WAND loop.
LANCE_FTS_MAXSCORE=0opts back into the classic loop.🤖 Generated with Claude Code