Refactor(benchmark): analyze and optimize existing test to enhance opcode count #1968
Description
Marius points out the following approach that could optimize some of the benchmark tests:
Call a contract A that calls into contract B
B executes 1024 times the opcode under test
B exits and returns back to A
A loops back and calls into B again
This is already in use, you can check the following cases:
- zero parameter opcode: Implementation & Analysis
- Blobhash operation: Implementation & Analysis
After reviewing all the test cases, I found several test cases that might be able to be optimized based on this idea: