Improve ZkTracer initialization time #720
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.
When doing load testing on eth_sendRawTransaction with transaction simulation enabled, we've noticed that ZkTracer takes more than 20% of the time, on loading the opcode and the spillings.
This RP Improves ZkTracer initialization time by doing only once Opcodes and spillings loading from disk resources. This is done when the class is loaded, opcodes and spillings are initialized is a static way.Fixes issue #716