3 ms·
Note to readers: This is a non-crypto hash algorithm. It's not meant to be cryptographically secure, but collision is rare enough for databases and similar app
by segfaultbuserr 6y ago
Note to readers: This is a non-crypto hash algorithm. It's not meant to be cryptographically secure, but collision is rare enough for databases and similar applications, and is really fast. A real crypto hash like SipHash or BLAKE is already considered lightning fast (1-3 GB/s) in crypto applications, but XXH is faster than a RAM sequential read (30+ GB/s).
- 5986043handy 6y agoYep, Blake3 can do around 6-7GB/s https://github.com/BLAKE3-team/BLAKE3 https://github.com/BLAKE3-team/BLAKE3
- MR4D 6y agoSo, does this mean I can replace CRC32 with XXH ?
- ncmncm 6y agoDepends what you use CRC for. CRC is processed a byte at a time, but really fast things nowadays do 16 or 32 bytes at a time.