This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Repository navigation
Optimize search traversal and expanded-term execution - #203
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Expanded-term queries repeatedly constructed posting views, copied metadata, and expanded dense bitmaps into document vectors. This change defers posting setup, keeps dense unions as bitmaps, avoids discarded dictionary-key allocations, and improves ranked-term traversal. It also adds bounded regex-prefix extraction, single-star matching, an opt-in Unicode-word tokenizer, regression coverage, and the collected benchmark evidence and reporting fixes.
Matched corpus screens show 1.62–1.83× faster dense prefix/wildcard counts and 1.70–1.76× faster prefix top-k after deferring posting views, with independent ARM fixture checks. These are successive measured checkpoints, not a claim that every query family has reached parity. Defaults and persisted index formats remain unchanged; experimental format probes and unfinished remote runs remain outside this commit.
Validation: the five-step search harness passed (formatting, strict Clippy, 2,075 native tests with 25 ignored, native without sync, and broker compilation). WASM release build and all 41 JavaScript tests passed. Full lifecycle/RPC validation was not rerun because no lifecycle or RPC implementation changed. Commit hooks passed except the deliberately skipped large-artifact limit and whitespace rewriting of exact patch snapshots; the benchmark data and patch bytes are retained.