release: 0.2.5830 performance groundwork - #675
Conversation
|
👋 Thanks for the contribution! Quick heads-up: this repo lands changes on the current Please retarget this PR via Edit → base branch to the active release branch (currently (Automated hint — reply here if you need a hand.) |
Benchmark Regression ReportThresholds: 10.00% and 50,000 ns absolute delta
|
Benchmark Regression ReportThresholds: 10.00% and 50,000 ns absolute delta
|
Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
Co-Authored-By: Codegraff <blackfloofie@codegraff.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7837a331b2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const gen = self.search_gen.load(.acquire); | ||
| if (self.word_render_cache.render(word, false, gen, allocator, out)) return; |
There was a problem hiding this comment.
Invalidate word cache when swapping indexes
If a codedb_word result is cached before replaceWordIndex() swaps in a different persisted word index, this cache is still keyed only by search_gen. replaceWordIndex() updates self.word_index/word_index_generation without changing search_gen, so a later lookup for the same word can return the pre-replacement postings from word_render_cache; include the word-index generation in the cache key or bump search_gen on every word-index replacement/invalidation.
Useful? React with 👍 / 👎.
Release 0.2.5830 — performance and parity guardrails
This PR targets
release/0.2.5829and prepares the complete 0.2.5830 release. The executable benchmark candidate isbc72bfca4f4dcb9316f2f00f0ca78ab18c4e3c74; PR head7837a33is its documentation-only evidence successor.Follow-up to #673.
Performance work
No ranking formula, result cap, parser behavior, path-security policy, telemetry behavior, or MCP response schema changes.
Final paired release gate
Twenty clean, counterbalanced AB/BA pairs compared production baseline
dd36e94through pinned harness-only baseline24e89c7against candidatebc72bfc, using the same fixed 21-file corpus and Zig0.17.0-dev.813+2153f8143.Persisted report:
docs/bench-0.2.5830-paired-report.mdFull methodology and transport measurements:
docs/performance-0.2.5830.mdVerification
zig build testzig build -Doptimize=ReleaseFastReleaseFastcross-buildzig build wasmgit diff --checkRelease preparation
0.2.5830in Zig, release info, and npm metadata