Introduce multiple block executor implementations #8
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
…ackend This avoids more unnecessary deps.
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.
This PR introduces various block execution strategies, basically the different combo of state backend (disk/in-memory) and block execution (runtime/off-runtime).
The initial idea was to leverage the in-memory backend for faster state root computation. However, the final performance boost on block execution was roughly less than 10x, with the memory usage skyrocketing to 43GB when the chain grows to block 430000+. The number is much lower than my expectation since the read/write of disk versus memory could be up to 1000x. This experiment of block execution optimization does not produce a satisfying full sync performance from genesis, we still need to dig into it.
There are a few leftovers that can be worked on later.