This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
lower default pruning history and memory #4528
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
--pruning-history: 1200 -> 64 --pruning-memory: 150 -> 75
rphmeier
added
A0-pleasereview 🤓
arkpar
added
A8-looksgood 🦄
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
--pruning-history:1200 -> 64--pruning-memory: 150 -> 75@arkpar This addresses memory issues while syncing through the attack blocks.
--pruning-historyis a minimum, so in general we will store far more states.We may want to insert a
shrink_to_fitcall somewhere for the backing overlay when we detect that the size is much smaller than capacity, currently there's a persistent ~100MB overhead after the attack blocks.