fix: prepared statements eviction CPU churn #712
Merged
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.
When prepared statements were frequently evicted, the algorithm that was calculating the memory usage for the prepared statement data structure iterated over every single statement in the cache. This was effectively O(n^2) in the worst case, and it was burning CPU to provide only an approximation.
This change uses a simpler algorithm to calculate memory usage that doesn't have to walk the entire data structure.