Avoid recomputing state.previous_epoch
#3256
Closed
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.
Issue Addressed
NA
Proposed Changes
Much to my surprise,
BeaconState::previous_epoch
has been showing up in flamegraphs! This PR removes repeated calls to it.Benchmarks
Benchmarks on a recent mainnet state using #3252 to get timing.
These tests were run with optimisations #3254 and #3255 already applied.
Without this PR
With this PR
Additional Info
per_epoch_processing
low-hanging-fruit #3254 and UseVec
inSingleEpochParticipationCache
rather thanHashMap
#3255