[Core] Clear EvoDB cache when oversized #2831
Merged
Conversation
This file contains 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
Fuzzbawls
changed the title
Liquid369
force-pushed
the
2023_evodb_cache
branch
from
de7288c
to
62defc8
Compare
panleone
approved these changes
Apr 17, 2023
Fuzzbawls
approved these changes
Apr 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Perpetual hunt to reduce memory!
This is a simple PR to clear the EvoDB cache and flush it to disk when it grows.
In Dash, users experience persistently growing memory because the EvoDB cache until v.18 dashpay#5007
This is flushing the evodb cache and chain state when hit its "critical" memory and will keep from persistently growing.