Improve performance of mock getOriginAddress, getCallerAddress #2287
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.
Description
Motivation and Context
The overloaded methods
getOriginAddress
andgetCallerAddress
inProgramInvokeMockImpl
perform hashing and secp256k1 base point multiplication each timeORIGIN
orCALLER
are executed.rskj/rskj-core/src/test/java/org/ethereum/vm/program/invoke/ProgramInvokeMockImpl.java
Lines 111 to 129 in 12c9b32
This makes these opcodes unnecessary slow and it impedes my effort to detect genuine performance issues with the EVM itself.
How Has This Been Tested?
With this test harness (rskj-core/src/test/java/co/rsk/vm/Poc.java):
Runtime before this fix: 10 minutes, 17 seconds
Runtime after this fix: 6 seconds
Using:
On Linux x64, Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Types of changes
Checklist: