Repository navigation
perf: simplify cache bookkeeping - #70
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 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.
Summary
Remove redundant index page dirty-state writes, skip unchanged managed-memory peak and net-zero L1 charge updates, and bypass shard locking and directory work when L1 has no entry capacity.
Partition locks continue to synchronize index bytes, warm close regenerates every page checksum, and charge transfers retain the existing exclusive-ownership and budget checks. Reuse the existing regression coverage, adding one bypass-count assertion to the zero-capacity L1 scenario.
Validation on macOS arm64:
cargo x check,cargo x test(372 Rust and 9 Python tests), andcargo x lintpassed, including dependency advisories. No throughput benchmark was run; the performance claims are limited to eliminating redundant operations.