core: concurrent database reinit from freezer dump #19604
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
rjl493456442
approved these changes
May 21, 2019
karalabe
force-pushed
the
freezer-reimport-fast
branch
from
6ff1580 to
0e5226c
Compare
karalabe
changed the title
19 tasks
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.
Our previous code reinitialized a new database from an old freezer sequentially. This turned out to be quite a heavy operation, taking
1h56m59.818sfor mainnet. This PR attempts to make block and transaction hashing concurrent, reaching a reinit speed of52m3.238s. That's kind of the limit of leveldb random inserts.