Speed up sync #2316
Open
Speed up sync #2316
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
|
Bencher Report| Branch | 2158-speedup-sync |
| Testbed | self-hosted |
Click to view all benchmark results
| Benchmark | Latency | Benchmark Result milliseconds (ms) (Result Δ%) | Upper Boundary milliseconds (ms) (Limit %) |
|---|---|---|---|
| full-blocks-erc20-transfers/full-blocks-erc20-transfers | 📈 view plot 🚷 view threshold | 1,447.10(+21.14%)Baseline: 1,194.52 | 1,595.83 (90.68%) |
| full-blocks-evm-transfers/full-blocks-evm-transfers | 📈 view plot 🚷 view threshold | 437.71(-2.99%)Baseline: 451.22 | 593.57 (73.74%) |
| full-blocks-zil-transfers/full-blocks-zil-transfers | 📈 view plot 🚷 view threshold | 4,106.50(+3.68%)Baseline: 3,960.87 | 5,320.34 (77.18%) |
| process-empty/process-empty | 📈 view plot 🚷 view threshold | 10.17(+9.19%)Baseline: 9.31 | 11.81 (86.11%) |
…istic and eventually degenerates to 1 peer.
…n for dynamic sizing.
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.
Speeds up Phase 1, by firing 10 concurrent requests at a time, processing 10 responses, then firing the next 10, etc. The speedup in this sense is fairly linear (at least up to 10), as expected. Since Phase 2 is CPU-bound, firing concurrent requests is unnecessary.
When processing the Phase 1 responses, it also splits the chain segment into sub-segments, based on the estimated response payload size. So, if there are large blocks, it will split the segment into several sub-segments for Phase 2 processing.
This removes support for V1 compatibility. Do not merge this until the hard-fork to >= 0.6.0