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.
Sorry for the intrusion but this is a interesting benchmark that you have made, it primarily tests and compares initialization part of sputnik and revm.
I didn't spend a lot of time on looking at that part in the start, mostly did optimization on the execution (interpreter) loop, but after tinkering some things on revm/forks (bluealloy/revm#191) branch and adding one more optimization in revm/precomp (bluealloy/revm@d851763) I am getting a lot better times:
It would be interesting to see how does it compare on executing heavy contracts, I would expect around x2 speedup but i didn't do the testing :) this is good candidate https://github.com/karalabe/snailtracer