Optimize account hash CumulativeOffset index from vec to 2-element array #33839
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.
Problem
Optimize
CumulativeOffset
for raw data index during accounts hash calculation.The raw data is at most 2d. Therefore, instead of using a Vec to store one or two indexes to the data, we can change it to use
[usize; 2]
.This saves heap allocation and one pointer deref when reading the index.
Summary of Changes
Use
[usize; 2]
forCumulativeOffset
Fixes #