go/worker/storage/config: Default to parallel chunking algorithm#6278
Draft
martintomazic wants to merge 1 commit intomasterfrom
Draft
go/worker/storage/config: Default to parallel chunking algorithm#6278martintomazic wants to merge 1 commit intomasterfrom
martintomazic wants to merge 1 commit intomasterfrom
Conversation
✅ Deploy Preview for oasisprotocol-oasis-core canceled.
|
martintomazic
commented
Jul 29, 2025
Contributor
Author
|
As discussed today, we should wait with this one until next release and test this with few canary nodes first. We could also lower chunker threads for consensus checkpoints (possibly to 1) given that consensus state is significantly smaller than e.g. what we have for runtimes. |
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.
Closes #6219
I ran the new chunking algorithm for a few days in the cloud, increasing checkpoint creation frequence 10x, and did a state sync from this node a few times.
This was done by having local and remote node both use new
checkpointsyncp2p protocol. Since they were the only two peers on the new protocol they automatically discovered each other.