-
Notifications
You must be signed in to change notification settings - Fork 1
perf: bound L1 cache access-history retention #1295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed — this is a valid, merge-blocking gap, not a false positive.
get()releases nothing on the TTL-expiry branch:delete()and the patched_evict_if_needed()bothpopthe history, but this path does not — so any key that expires by TTL orphans itsaccess_patterns[key]with no cache entry left to ever trigger cleanup. That is precisely the leak this PR sets out to bound, still open for expiring entries, so the "history footprint proportional to resident keys" guarantee does not hold once TTLs are in play.Minimal in-scope fix — mirror the eviction path:
Suggested regression (parallels
test_evicted_key_history_is_released):set()a key with a shortttl, forceexpires_atinto the past,get()it (asserting theNone/miss), then assertkey not in cache.access_patterns.Separate, pre-existing observation worth a follow-up rather than folding in here: this same expiry branch also never decrements
stats.total_entries/stats.total_size_bytes, so an expired-then-get()'d entry leaves the byte/entry accounting overstated until the nextset()of that key. That predates #1295 and is out of its stated scope — flagging it, not asking for it in this PR.Once the
popand its regression land, this PR is clean; nothing else here is blocking.Generated by Claude Code