makeself VS amazon-corretto-crypto-provider

Why not try a self-extracting archive?

see https://makeself.io

Thanks for introducing Zerobrane, really looks fantastic. Also by extension introduced me to https://makeself.io/ for making Linux installations.

Yeah, I can understand that, but the same advantage doesn't easily apply to situations like Rust, where you're already quite unlikely to be building the program on your production machines. I've done the same for Python many times, actually, using pip download to retrieve dependencies and building a package that is then installed on the target machine with some makeself mess. It actually worked surprisingly well, much of the time.

edit: you might wanna check out makeself

I don't fully agree for two reasons.

First, I am not sure the data on most in-use hardware (e.g. EC2 m5/c5/i3en etc ...) supports your conclusions. xxHash is faster than crypto hashes always and BLAKE3 single threaded is faster on every Intel machine I've come across in wide deployment. I hear similar arguments around CRC-32 and to be frank it just isn't true on most computers most people run things on.

Second, many languages don't properly use the hardware instructions and if they do they often don't use them correctly. For example, Java 8 has bog slow SHA-1, AES-GCM and MD5 implementations, and switching to Amazon Coretto Crypto Provider was able to speed SHA/MD5 up by 50% and AES-GCM by ~90% on a reasonably large deployment (although the JDK wasn't using proper hardware instructions for AES-GCM until Java 9 I think it is still slower even after that).

That being said, like I disclaimed at the top of the benchmark your particular hardware and your particular language matters a lot.

[1] https://github.com/corretto/amazon-corretto-crypto-provider/...

If you need better performance (and are running Linux), use the Amazon Corretto Crypto Provider (disclaimer: I am one of its primary authors)