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.
This PR adds a speed test for xxhash3, latest implementation from
twox-hash
, and renames the existing test toxxhash64
.Some results from my machine,
AMD Ryzen 9 5900X, 32GB DDR4-3000 (16-17-17-35)
I feel like there should be some sort of disclaimer somewhere around the benchmark code that this measures the
Hasher
streaming interface, rather than pure throughput. The code is omitting theoneshot
APIs, where certain algorithms like the xxh3 implementation benefit severely.In any case, I did also benchmark xxh3 oneshot out of curiosity. xxh3 oneshot sits between wyhash and rapidhash for most inputs; before starting to run away from other stable algorithms at 512 bytes.
Short String Performance (2-64 characters)
Long String Performance (100+ characters)
Miscellaneous Types (u64 and object)