<p>I was googling around for code examples using the crypto package and found <a href="https://blog.cloudflare.com/go-crypto-bridging-the-performance-gap/" rel="nofollow">this 2014 post on Cloudflare's blog.</a></p>
<p>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. </p>
<p>There was another statement in here about Go crypto performance not being as good as OpenSSL.</p>
<p>Curious if anybody knows the state of the crypto package as of 1.9.2, and if anything's changed / improved there. </p>
<hr/>**评论：**<br/><br/>dgryski: <pre><p>I believe the majority of Cloudflare's performance work has been merged back into the standard library.</p></pre>dirty_owl: <pre><p>Thanks!</p></pre>UltraNemesis: <pre><p>Not benchmarks, but here is another blog entry from Cloudflare</p>
<p><a href="https://blog.cloudflare.com/exposing-go-on-the-internet/" rel="nofollow">https://blog.cloudflare.com/exposing-go-on-the-internet/</a></p></pre>PaluMacil: <pre><p>Main quote for your topic being:</p>
<blockquote>
<p>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.</p>
</blockquote></pre>kostix: <pre><p>You may look at this post <a href="https://blog.cloudflare.com/arm-takes-wing/" rel="nofollow">https://blog.cloudflare.com/arm-takes-wing/</a> which is one month old.</p>
<p>It's about Go's crypto performance on ARM64 but the charts can be used to compare recent Go to OpenSSL.</p></pre>
