xxh VS xxHash

Cool, thanks! It would also be nice to list a few comparison points to xxh in the readme.

Oh but you can! https://github.com/xxh/xxh

How does this compare to xxh?

To solve the ssh problem there’s xxh which scp’s a portable shell of your choosing before starting an interactive session with it on the server.

There are various features that make the terminal experience feel more modern. Unlike your meme replies, BASH does support jumping across words with CTRL+Arrow Keys. For remote hosts, you can try xxh. But if you're so callous as to not even consider adjusting yourself to use shift+ctrl+c instead of ctrl+c, well then I really don't know what yo tell you.

Maybe give xxh a try?

There is also this other thing but the zsh or ohmyzsh plugin didn't work because I was using it on macOS which doesn't have XDG directories predefined and it also requires sshpass to carry over the files (when using password to ssh) because it probably uses other methods to carry over your files, didn't look into it: https://github.com/xxh/xxh

I'd also like to drop this here: https://github.com/xxh/xxh

> 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.