-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Benchmark #1
Comments
@pjanx Meow is a Non-cryptographic hash function, so SipHash is not comparable http://wikipedia.org/wiki/List_of_hash_functions#Non-cryptographic_hash_functions |
@cup It is still a hash function and up for comparison, if only for curiosity reasons. |
SipHash is not a fast hash function, so it's not a particularly useful datapoint. Their "faster version of SipHash" is HighwayHash and it is only 4 bytes per cycle. Meow hash is 16 bytes per cycle, or roughly 4 times faster in cache. Out of cache, Meow still wins, but it gets slowed down to memory throughput speed, which varies per CPU so it's hard to quote a particular number. Modern CPUs can usually deliver memory faster than 4 bytes per cycle, though, so Meow typically still beats 4bpc hashes like Highway et al. |
here are some that might be worth comparing |
Really not sure what you're asking for here, because all of these hashes post statistics, as does Meow. But to summarize, Meow is much faster than everything you posted, and it generates larger hashes as well. In most cases you can tell that just from reading the web pages you posted :) Again, Meow is 16 bytes/cycle for up to 512-bit hash. The hashes you posted all generate smaller hashes at less bytes per cycle. How much slower they are depends on how big of a hash you ask them to make, because most of them get slower for larger hash outputs, while Meow does not (it is the same speed for any hash size up to 512 bits). |
from http://mollyrocket.com/meowhash:
ok that is great - but what are we comparing it against
would be nice to see what the competitors are and/or what the methodology was
thanks
The text was updated successfully, but these errors were encountered: