hash-prospector VS xxHash

But for good general purpose hash functions, you can also take a look at u/skeeto's prospector project.

Special thanks to hash-prospector for inspiration and useful information.

A project to keep an eye on in the future. The -search command is very much like my own hash search, plugging different constants into xmxmx.

Maybe look at https://github.com/skeeto/hash-prospector https://www.reedbeta.com/blog/hash-functions-for-gpu-rendering/

New best known functions

https://github.com/skeeto/hash-prospector (recently outdone)

Where each 0xXXXXXXXX is a random, odd 32-bit integer. Not all choices are equal, and you can find some excellent xmx parameters here: https://github.com/skeeto/hash-prospector/issues/19

For my stack based texture generator I used (utilizing https://github.com/skeeto/hash-prospector )

  let intHash = x => {

This is one of the best known hashes for 32 bit integers. See https://github.com/skeeto/hash-prospector and https://nullprogram.com/blog/2018/07/31/

> GPU Hash Table?

How bad would performance have suffered if you sha256'd the lines to build the map? I'm going to guess "badly"?

Maybe something like this in CUDA: https://github.com/Cyan4973/xxHash ?

Examples of fast, simple hashes that are independent enough includes murmur, xxHash, Fowler–Noll–Vo hash function and many others

If you're only using the hash for non-cryptographic applications, there are much faster hashes: https://github.com/Cyan4973/xxHash

I found the benchmark result of AMD ryzen 5950X

But what's the catch, you're thinking ? Well, it is a bit slower than its counterparts when it comes to deserializing (and marginally faster for serializing). To achieve smaller footprint, it uses a few tricks and notably a custom hash table to deduplicate strings. This comes at a cost of course (even when featuring xxHash to speed things up), but keeps the slowdown reasonable (I think).

Non cryptographic hashes has collisions, for example, assume you having content like "abcdefg" which hashed value is "123", in case of weak hash algorithm some other content like "abcdefZ" can also have a hash "123" which basically means such hash function is failed to be unique fingerprint of particular content. BLAKE3 for example can do 6-7Gb/s which make it pretty fast and secure. If your requirement accepts collision with defined error rate, I would advise you to take a look at XXH3 if you need very snappy hash algorithm, which can run at pace or RAM access (30GB/s+), but again, run tests at particular equipment you targeting, may be AES hardware accelerated MeowHash will serve you better.