#1 2024-05-16 07:51:01

TPrami
Member
Registered: 2010-07-06
Posts: 114

XXH3_64bits() really flies

Offline

#2 2024-05-16 08:01:55

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,355
Website

Re: XXH3_64bits() really flies

Not sure it is a fair comparison.
For instance, they use non-parallel version of crc32c.

On my Core i5, here are some numbers of the diverse built-in in mORMot 2:

     2500 crc32c in 157us i.e. 15.1M/s or 33 GB/s
     2500 xxhash32 in 590us i.e. 4M/s or 8.8 GB/s
     2500 crc32 in 157us i.e. 15.1M/s or 33 GB/s
     2500 adler32 in 152us i.e. 15.6M/s or 34.1 GB/s
     2500 hash32 in 326us i.e. 7.3M/s or 15.9 GB/s
     2500 aesnihash in 93us i.e. 25.6M/s or 55.8 GB/s
     2500 md4 in 5.45ms i.e. 447.8K/s or 0.9 GB/s
     2500 md5 in 6ms i.e. 406.6K/s or 886.1 MB/s
     2500 sha1 in 2.27ms i.e. 1M/s or 2.2 GB/s
     2500 hmacsha1 in 2.53ms i.e. 0.9M/s or 2 GB/s
     2500 sha256 in 2.48ms i.e. 0.9M/s or 2 GB/s
     2500 hmacsha256 in 2.76ms i.e. 883.9K/s or 1.8 GB/s
     2500 sha384 in 7.31ms i.e. 333.8K/s or 727.4 MB/s
     2500 hmacsha384 in 8.62ms i.e. 283K/s or 616.8 MB/s
     2500 sha512 in 7.31ms i.e. 333.6K/s or 727 MB/s
     2500 sha512_256 in 7.31ms i.e. 333.7K/s or 727.2 MB/s
     2500 hmacsha512 in 8.62ms i.e. 283.1K/s or 617.1 MB/s
     2500 sha3_256 in 10.79ms i.e. 226.1K/s or 492.7 MB/s
     2500 sha3_512 in 19.68ms i.e. 124K/s or 270.3 MB/s

As you can see, our aesnihash reaches 55.8 GB/s on a Core i5 with a proven hash algorithm taken from the golang runtime.
And for hashing data in memory, it has the advantage (requirement?) of being secure against hash flooding http://ocert.org/advisories/ocert-2012-001.html

Note that sha1/sha256 numbers are very high on my PC because its CPU features SHA-NI.
And note that our xxhash32() version is a pretty simple implementation without any unrolling. But is gives a test of our Core i5 raw speed in respect to the Core i7 used for the tests on your links.

Offline

#3 2024-05-16 10:40:00

TPrami
Member
Registered: 2010-07-06
Posts: 114

Re: XXH3_64bits() really flies

Hard to tell are those parallel or non-parallel versions. What they publish.

SSE2 and New AVX (what ever it was) optimizations give quite nice boost.

     2500 crc32c in 157us i.e. 15.1M/s or 33 GB/s

Don't understand those values, 15M/s or 3GB/s, would need header for table/and table smile

-Tee-

Offline

#4 2024-05-16 14:35:26

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,355
Website

Re: XXH3_64bits() really flies

15M/s = 15 millions of hashes per seconds = per call speed
3GB/s = 33 GigaBytes per second = per data size speed
Our benchmark run on several data sizes, so the absolute performance is likely to be higher.

I don't see any reason to change our AesNiHash with those XXH3_64 which are pretty much experimental and likely to be slower.

Offline

#5 2024-05-17 08:11:39

TPrami
Member
Registered: 2010-07-06
Posts: 114

Re: XXH3_64bits() really flies

ab wrote:

15M/s = 15 millions of hashes per seconds = per call speed
3GB/s = 33 GigaBytes per second = per data size speed

Ah, makes sense, thanks.

-Tee-

Offline

Board footer

Powered by FluxBB