@@ -49,7 +49,7 @@ On Intel Sapphire Rapids CPU, on `xlsum.csv` dataset, the following numbers can
4949| ` aHash::hash_one ` | 64 | ❌ | 1.23 GiB/s | 8.61 GiB/s |
5050| ` foldhash::hash_one ` | 64 | ❌ | 1.02 GiB/s | 8.24 GiB/s |
5151| ` gxhash::gxhash64 ` | 64 | ❌ | __ 2.68 GiB/s__ | 9.19 GiB/s |
52- | ` stringzilla::hash ` | 64 | ✅ | 1.84 GiB/s | __ 11.23 GiB/s__ |
52+ | ` stringzilla::hash ` | 64 | ✅ | 1.84 GiB/s | __ 11.38 GiB/s__ |
5353| | | | | |
5454| Python 🐍 | | | | |
5555| ` hash ` | 32/64 | ❌ | 0.13 GiB/s | 4.27 GiB/s |
@@ -66,19 +66,19 @@ On Intel Sapphire Rapids CPU, on `xlsum.csv` dataset, the following numbers can
6666In larger systems, however, we often need the ability to incrementally hash the data.
6767This is especially important in distributed systems, where the data is too large to fit into memory at once.
6868
69- | Library | Bits | Ports ¹ | Short Words | Long Lines |
70- | -------------------------- | :---: | :-----: | -------------: | -------------: |
71- | Rust 🦀 | | | | |
72- | ` std::hash::DefaultHasher ` | 64 | ❌ | 0.51 GiB/s | 3.92 GiB/s |
73- | ` aHash::AHasher ` | 64 | ❌ | __ 1.30 GiB/s__ | __ 8 .56 GiB/s __ |
74- | ` foldhash::FoldHasher ` | 64 | ❌ | 1.27 GiB/s | 8.18 GiB/s |
75- | ` crc32fast::Hasher ` | 32 | ✅ | 0.37 GiB/s | 8.39 GiB/s |
76- | ` stringzilla::Hasher ` | 64 | ✅ | 0.89 GiB/s | 6.39 GiB/s |
77- | | | | | |
78- | Python 🐍 | | | | |
79- | ` xxhash.xxh3_64 ` | 64 | ✅ | 0.09 GiB/s | 7.09 GB/s |
80- | ` google_crc32c.Checksum ` | 32 | ✅ | 0.04 GiB/s | 5.96 GiB/s |
81- | ` stringzilla.Hasher ` | 64 | ✅ | __ 0.35 GiB/s__ | __ 6.04 GB/s__ |
69+ | Library | Bits | Ports ¹ | Short Words | Long Lines |
70+ | -------------------------- | :---: | :-----: | -------------: | -------------- : |
71+ | Rust 🦀 | | | | |
72+ | ` std::hash::DefaultHasher ` | 64 | ❌ | 0.51 GiB/s | 3.92 GiB/s |
73+ | ` aHash::AHasher ` | 64 | ❌ | __ 1.30 GiB/s__ | 8 .56 GiB/s |
74+ | ` foldhash::FoldHasher ` | 64 | ❌ | 1.27 GiB/s | 8.18 GiB/s |
75+ | ` crc32fast::Hasher ` | 32 | ✅ | 0.37 GiB/s | 8.39 GiB/s |
76+ | ` stringzilla::Hasher ` | 64 | ✅ | 0.89 GiB/s | __ 11.03 GiB/s __ |
77+ | | | | | |
78+ | Python 🐍 | | | | |
79+ | ` xxhash.xxh3_64 ` | 64 | ✅ | 0.09 GiB/s | 7.09 GB/s |
80+ | ` google_crc32c.Checksum ` | 32 | ✅ | 0.04 GiB/s | 5.96 GiB/s |
81+ | ` stringzilla.Hasher ` | 64 | ✅ | __ 0.35 GiB/s__ | __ 6.04 GB/s__ |
8282
8383For reference, one may want to put those numbers next to check-sum calculation speeds on one end of complexity and cryptographic hashing speeds on the other end.
8484
0 commit comments