spv: Process header batches in parallel #2311
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
matheusd
commented
Dec 4, 2023
matheusd
force-pushed
the
async-headers
branch
from
751e5fe to
a85a6b7
Compare
jrick
reviewed
Dec 4, 2023
jrick
reviewed
Dec 4, 2023
matheusd
force-pushed
the
async-headers
branch
2 times, most recently
from
8d9b54d to
4aeb5cb
Compare
This switches the initial SPV header fetching process to process each batch of headers in parallel through its various stages.
matheusd
force-pushed
the
async-headers
branch
from
4aeb5cb to
ab15d98
Compare
jrick
approved these changes
Dec 5, 2023
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 switches the initial SPV header fetching process to process each batch of headers in parallel through its various stages.
The initial header sync process is split into a 3-stage pipeline, where batches of headers progress through. Each stage is run on a separate goroutine, providing some parallelism for the entire process.
The following is a rough comparison of sync times with/without this PR (all on mainnet, reference master):
Part of #2289.