I was googling around for code examples using the crypto package and found this 2014 post on Cloudflare's blog.
They apparently forked Go and built their own elliptic curves and AES-GCM in assembly for amd64. They have a table showing their implementation's performance improvements over Go 1.4.2.
There was another statement in here about Go crypto performance not being as good as OpenSSL.
Curious if anybody knows the state of the crypto package as of 1.9.2, and if anything's changed / improved there.
评论:
dgryski:
dirty_owl:I believe the majority of Cloudflare's performance work has been merged back into the standard library.
UltraNemesis:Thanks!
PaluMacil:Not benchmarks, but here is another blog entry from Cloudflare
kostix:Main quote for your topic being:
Back when crypto/tls was slow and net/http young, the general wisdom was to always put Go servers behind a reverse proxy like NGINX. That's not necessary anymore! ...it's now really fast..., and its security track record so far is excellent.
You may look at this post https://blog.cloudflare.com/arm-takes-wing/ which is one month old.
It's about Go's crypto performance on ARM64 but the charts can be used to compare recent Go to OpenSSL.
