Skip to content

Commit 2b19019

Browse files
committed
Docs: 4.0.15 StringZilla hash speeds
1 parent 5e8cbcf commit 2b19019

File tree

2 files changed

+16
-14
lines changed

2 files changed

+16
-14
lines changed

.vscode/settings.json

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,11 @@
66
"byteset",
77
"bytesets",
88
"bytesum",
9+
"cityhash",
910
"corasick",
1011
"CUDF",
1112
"Dataframe",
13+
"foldhash",
1214
"Gotoh",
1315
"gxhash",
1416
"lexsort",

README.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -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
6666
In larger systems, however, we often need the ability to incrementally hash the data.
6767
This 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

8383
For 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

Comments
 (0)