Repository navigation
perf(xor): reduce peak construction memory - #316
Merged
Merged
Conversation
tisonkun
changed the title
tisonkun
enabled auto-merge (squash)
October 30, 2026 09:28
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
XOR construction retained its graph buffers while allocating the final fingerprint payload. Release the graph after peeling succeeds, when assignment only needs the peel stack.
For eight million distinct synthetic hashes with base seed 1, measured peak live heap allocation changes as follows:
Measurements use allocation tracking on arm64 macOS and exclude the preexisting input and allocator overhead; they are not process RSS. A separate 16,384-key case exercises retry cleanup at all three widths.
Validation:
cargo x check,cargo x test,cargo x lint, and targeted MSRV 1.86 tests.