Use LRUCache in ExpressionParser for efficient memory usage #6667
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.
Fixes #6656
Description
This PR addresses a memory leak issue in the
ExpressionParser
class. Previously, theExpressionParser
class used aConcurrentDictionary
to cache parsed expressions, which could lead to excessive memory usage over time. This PR changes theExpressionParser
class to use anLRUCache
instead, which has a maximum capacity and uses a least-recently-used policy to evict entries from the cache when the maximum capacity is reached. This change should help to mitigate the memory leak issue.Specific Changes
ExpressionParser
class to use anLRUCache
instead of aConcurrentDictionary
for caching parsed expressions.Testing
This change was tested using a console application that demonstrates the memory leak issue in
ExpressionParser
:https://github.com/jamesemann/expression-parser-leak
Before:
After: