Improve pruning: performance, config and progress logging #328
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.
part of NIT-2541
This PR:
enables cleans cache in triedb used for traversing storage tries in
dumpRawTrieDescendants
- when opening storage trie withtrie.NewStateTrie
(using the trick above), a node with hash equaldata.Root
is read twice from triedb (once in when getting atrie.Reader
, then when reading the node). Caching the node should save some of KeyValueStore reads.adds
pruner.Config.Threads
optionadds extra progress logging when a thread traversing storage trie for given account takes longer then 5 minutes