lru: fix expiry when updating#82
Merged
sergiosalvatore merged 1 commit intovimeo:masterfrom Feb 10, 2026
Merged
Conversation
Fix an oversight. When updating an existing value, we forgot to update the expiry. Fortunately, this wasn't a problem for Galaxycache's main use-case, but, the omitted expiry handling had two issues: - We ended up with extra entries in the heap for each update with an expiry. - We had the wrong expiration time stored on the entry in the LRU, so it would expire too early independent of the value in the heap.
|
Interesting -- Sean, Justin and I were just looking at a potential memory leak where after a day or so, it seemed like GC and garbage collection was getting out of hand. We weren't able to get a profile in time. Perhaps this is related... |
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
2 participants
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.
Fix an oversight. When updating an existing value, we forgot to update the expiry.
Fortunately, this wasn't a problem for Galaxycache's main use-case, but, the omitted expiry handling had two issues: