xxHash VS swift-crypto

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

dependencies: [ .package(url: "https://github.com/scade-platform/swift-java.git", branch: "main"), .package(url: "https://github.com/apple/swift-crypto.git", .branch("main")) ]

Are you aware of SwiftCrypto (granted it is missing some capabilities)?

swift-crypto is open source, not closed source. I dont work at Apple, but I’m a contributor: https://github.com/apple/swift-crypto/graphs/contributors

Apple is investing a lot in it, but Swift is much younger than Rust (especially as an open source project). There is a working group that meets every few weeks to shepherd the various projects. Most of the recent activity has been (AFAICT) about orchestration. Well, that and transitioning projects to use async/await and structured concurrency. Here's some recent activity in the Swift on server space:

- the proposal for distributed actors is currently in-review (https://github.com/apple/swift-evolution/blob/main/proposals...)

- a metrics API for backends like Graphite, Prometheus, etc. (https://github.com/apple/swift-metrics)

- HTTP/2 support for SwiftNIO (https://github.com/apple/swift-nio-http2)

- a new service discovery API (https://github.com/apple/swift-service-discovery)

- a new distributed tracing API (https://github.com/apple/swift-distributed-tracing)

- a Linux implementation of Apple's CryptoKit API on top of BoringSSL (https://github.com/apple/swift-crypto)

I'm not pretending that it's taking the server-side world by storm, but there is a fair amount of ongoing activity Personally, I'm using it for a couple personal projects and it's been solid, but I'm already a macOS developer, so it wasn't a big stretch for me to reach for it.

This doesn’t exactly answer your question, but you could always use swift-crypto for RSA.