mbo/hash: authoritative M5 Pro + Zen5 measurements; published multi-machine README - #251
Merged
Conversation
…s; published README First real per-machine measurement data under the new scheme: two authoritative bundles (clean main 1417af5) - Apple M5 Pro / clang-22 and AMD Ryzen 9 9950X / gcc-15 - committed via Git LFS, and the hash README performance section rendered from them by `publish` (one labeled block per machine: charts + curated tables). Dropped the old hand-maintained single-machine tables and the CI cross-platform section (both superseded by the two real machine blocks) and generalized the prose. `verify` confirms the committed charts match the bundle data.
Each per-machine benchmark section repeats the same table subheadings (64-bit / 128-bit / latency) under a different machine heading. Those are not real duplicates, so scope MD024 to actual siblings.
… PASS A SMHasher3 log with no "Overall result" line means the battery never completed (unknown hash name -> "Invalid hash '...' specified" which still exits 0, a crash, or truncation). Defaulting that to PASS on returncode 0 hid the failure; treat a missing verdict line as FAIL instead.
…urHash3-128)
The container binary rejects the bare names `FNV-1a` and `MurmurHash3`
("Invalid hash '...' specified"), so those two batteries never ran. Use the
variant-qualified names it registers, confirmed against `SMHasher3 --list`;
the bit-widths match the README (fnv1a 64 -> FNV-1a-64, murmur3 128 ->
MurmurHash3-128). A battery re-run is still needed to refresh the bundle data.
…e-time enforcement
Fab-Cat
approved these changes
Jul 11, 2026
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
2 participants
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.
The first real per-machine measurement data under the new scheme, and the last PR before tagging
0.13.0.main@1417af5e), Git-LFS: Apple M5 Pro / clang-22 (arm64) and AMD Ryzen 9 9950X / gcc-15 (x86_64).publish- one labeled block per machine (charts with the machine identifier + curated tables).verifyconfirms the committed charts match the bundle data.After this merges, the version triple (
MODULE.bazel=CHANGELOG.md=0.13.0) is aligned to tag.