Skip to content

Optimize retained size of Merkle trees#28260

Draft
fmeum wants to merge 19 commits intobazelbuild:masterfrom
fmeum:optimize-merkle-tree-memory
Draft

Optimize retained size of Merkle trees#28260
fmeum wants to merge 19 commits intobazelbuild:masterfrom
fmeum:optimize-merkle-tree-memory

Conversation

@fmeum
Copy link
Collaborator

@fmeum fmeum commented Jan 12, 2026

No description provided.

@fmeum fmeum force-pushed the optimize-merkle-tree-memory branch 13 times, most recently from fad85fc to 002be10 Compare January 17, 2026 18:35
fmeum added 17 commits February 14, 2026 15:51
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.

# Conflicts:
#	maven_install.json
@fmeum fmeum force-pushed the optimize-merkle-tree-memory branch from 34a8f15 to aab10a3 Compare February 14, 2026 14:52
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This pull request has been marked as stale since it has not had any activity in the last 30 days. It will be closed in the next 30 days unless any other activity occurs. If you think this PR is still relevant and should stay open, please post any comment here and the PR will no longer be marked as stale.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Mar 17, 2026
@fmeum fmeum removed the stale Issues or PRs that are stale (no activity for 30 days) label Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant