Draft
Conversation
Contributor
Author
|
Some stats: First 100k blocks, including processing: at ~13.8M range, without block processing however With block processing it drops to 12-16bps |
To be heavily cleaned up, very quick version to make a streaming version work instead of the previous version which would do batches of 8192.
ec65b67 to
ca10478
Compare
This file contains hidden or 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
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.
Improved version of #2910 where we no longer download and process blocks per 8192 but instead have a more streaming approach of downloading and processing blocks which should allow for more consistent bandwidth usage (well, not fully as it still relies on synchronous block processing).