Andrew7234/parallelize data fetch #736
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
Andrew7234
force-pushed
the
andrew7234/parallelize-data-fetch
branch
from
7344092 to
5755374
Compare
changelog make linter happy
Andrew7234
force-pushed
the
andrew7234/parallelize-data-fetch
branch
from
37c968d to
e452502
Compare
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.
Fetching data for a single block in consensus takes ~2.2 sec according to grafana:
This PR parallelizes some of the grpc calls. Based on local testing using the port-forwarded node, the per-block time averages around 1.2sec, with occasional spikes to 1.9.