fix: cap analytics in-memory cache at 1000 entries to prevent OOM#737
Merged
OlaGreat merged 1 commit intoJun 30, 2026
Merged
Conversation
|
@olywales-stack Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
The analytics in-memory cache was unbounded — every unique (profileId, startDate, endDate) combo inserted a permanent entry, risking OOM under load or targeted abuse.
CACHE_MAX_SIZE = 1000constant. After eachset(), if the cache exceeds the limit the oldest inserted entry (first key in Map insertion order) is evicted, keeping memory use bounded.Closes #674