Enable parallel state root computation by default#4247
Merged
Conversation
bhartnett
commented
May 15, 2026
| parallelStateRootComputation* {. | ||
| hidden | ||
| defaultValue: false | ||
| defaultValue: true |
Contributor
Author
There was a problem hiding this comment.
@advaita-saha How has your node been going with this enabled so far? Do you think we should make this enabled by default?
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
1 participant
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.
I've been testing the parallel state root computation for a while now and it has been running well so far. Perhaps now is a good time to enable it by default.
It can cause an increase in memory usage in some scenarios and in the worst case goes from around 16G when the caches are full to around 24G.
The speed up is somewhere between 2-4x when using 16 cores/threads. For the large stateroot computation on startup the speed up is around 2x because writing to the database is the bottleneck in that case but when most keys are in memory we can get 3-4x speedup.