Separate reading & writing into scoped threads #1129
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
|
Without this PR, the initial sync takes ~4h50m (excluding ~1h of full compaction). |
If the index is on a SSD, sync perfomance should improve.
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.
If the index is on a SSD, sync perfomance should improve.
When the blocks' data is stored on a HDD, it takes ~3h to finish the initial sync (without full compactions, which take an additional ~1h):
Most of the time is spent waiting for p2p messages (i.e. bitcoind reading blocks from the spinning disk):
Writing the index is done in parallel with the reading:
