perf: optimize syncing from L1 #665
Draft
Conversation
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
to avoid message too large errors
MrPiNkY2022
approved these changes
Sep 18, 2022
| @@ -3479,13 +3481,15 @@ dependencies = [ | |||
|
|
|||
| [[package]] | |||
| name = "opentelemetry" | |||
| version = "0.16.0" | |||
|
Can you update this PR? |
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.
Optimize syncing from L1 by pipelining ckb/ckb-indexer requests and the actual syncing.
Generally, syncing should be a bit faster.
This is particularly helpful when ckb/ckb-indexer request-response time is bit high, cc #507.
(This also updates opentelemetry-jaeger and enables batch auto split to avoid message too large errors when exporting trace spans to jaeger.)