cmd/evm: make batched state-test execution possible #27318
Merged
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 implements a feature that is already present in both nethermind and besu: the ability to run several state-tests in one instance.
For state-tests that are reasonably small, this makes a huge difference. Here's 1000 executions of a state-test which has a run-length of merely
28
steps.Nearly one minute versus
<2seconds
. When running it in a fuzzing-setting, the speedups is less marked, somewhere in the1x-2x
region.If the kzg stuff now has a static overhead, as suggested in #27258, this PR would definitely help (the fuzzer). Perhaps something similar can be done for
evm t8n
too.