Work on db replay #2284
Merged
Work on db replay #2284
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
ineiti
force-pushed
the
speedup_replay
branch
7 times, most recently
from
53b07dc to
13469e1
Compare
- clean up the different backward-compatible but used nowhere extensions of `StateReplay` - add all blocks to the skipchain.db, so that contracts using 'ReadOnlySkipchain' work - by default doesn't verify the forward link signature of blocks, as this is very costly, and can be supposed to be correct if its in 'cached.db' - use a memory state trie instead of a disk state trie when replaying -> much faster - can discard, write, resume blocks This makes replaying the current chain having 50k blocks possible in about 30' on a fast machine.
tharvik
approved these changes
May 22, 2020
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.
This PR does the following for 'bcadmin db replay':
StateReplayand can be supposed to be correct if its in 'cached.db'
This makes replaying the current chain having 50k blocks possible in about 30' on a fast machine.