perf: query cache O(1) LRU optimization #91
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.
This PR significantly improves the performance of the
QueryCacheby refactoring the Least Recently Used (LRU) eviction logic.1. O(1) LRU Implementation
accessOrderarray to track usage. This requiredindexOfandspliceoperations (O(N)) on everyget()andset()call. As the cache size grew, these linear scans became a performance bottleneck.Mapproperty, which maintains insertion order. By deleting and re-setting an entry, we move it to the "Most Recently Used" (end of map) position in O(1) time. Eviction is performed by deleting the first entry inMap.keys(), also O(1).Result: Constant-time cache operations and reduced code complexity.