Optimize retained size of Merkle trees #28260
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fmeum
force-pushed
the
optimize-merkle-tree-memory
branch
12 times, most recently
from
3f800fb to
f114ea8
Compare
By using JOL, the precise memory footprint of a `MerkleTree.Uploadable` can be measured in a unit test. This will serve as the basis for future memory improvements, with the aim of reducing peak heap usage while a `MerkleTree.Uploadable` is retained during the upload to the remote cache. This change also includes small tweaks to the `MerkleTree` interface that make future changes to its internals more transparent. It also makes some unit tests more realistic, which again prepares for future improvements.
fmeum
force-pushed
the
optimize-merkle-tree-memory
branch
from
fad85fc to
002be10
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.