[Question] Go applications on ARM-servers. Any reason not to?

<p>Hello,</p> <p>To start off: Go is a great language. I love learning more about engineering software, and computing as a whole with this language. Leveraging Go, I plan to write an application for a wider community.</p> <p>On prospecting deployment options, I&#39;ve come across an ARM-architecture server offering that boasts access to a huge amount of CPU cores at an affordable price: 96-cores (2.0 Ghz) at £300/month. The option I&#39;m seeing here, seems to blow any comparable offerings from Google&#39;s Container Engine (GCE) out of the water.</p> <p>I&#39;m not as well versed in computers, so apologies if I&#39;m overlooking something trivial. I&#39;m asking this Reddit community for help in understanding anything I&#39;m missing. Are there any reasons to be careful about developing a Go application for the ARM architecture?</p> <p>I can handle low-level explanations, and I learn best using analogies. Currently I understand as much as this video describes: <a href="https://www.youtube.com/watch?v=X4BxUiqWq8E" rel="nofollow">https://www.youtube.com/watch?v=X4BxUiqWq8E</a></p> <p>I hope this post serves as good learning material for others in the same position. Thank you very much for reading.</p> <hr/>**评论：**<br/><br/>eziopcmr: <pre><p>Go works well on ARM in terms of functionality but if you care about performance especially for https servers you may want to wait a bit. There are multiple assembly improvements coming from the ARM developers themselves (based on the CLs I&#39;ve seen) that should make it into the Go 1.11 release. </p> <p>I&#39;ve seen multiple ones on the crypto front which has been a sore point in terms of TLS performance. Cloudflare had a good blog post about it last week as they are evaluating the use of ARM servers instead of amd64 ones</p> <p>All that said I&#39;m definitely looking into tinkering with Go on ARM as well. Got it installed on my dragonboard 410c without problems :)</p></pre>kBenny5: <pre><p>Having read your comment, I begin to wonder if there’s little trouble in delaying ARM adoption until these improvements are released. Doesn’t seem to be much to worry in development, considering your code gets built for a target architecture. If there’s no additional hurdles to jump, then adopting ARM seems to be straightforward at the build stage.</p> <p>This also makes me eager to see future mobile and embedded applications written in Go. Open-source projects like runc and Kubernetes prove a lot about what is possible, and I believe Gophers will chew through the levels of complexity present in app development. I saw a GUI library for Go that leveraged HTML and stylesheet descriptions not too long ago!</p> <p>I’ll look into the Change Lists concerning future releases of Go. Cheers!</p></pre>sbinet: <pre><p>Out of curiosity, do you have a link to that GUI library?</p></pre>kBenny5: <pre><p>[To be updated]</p> <p>Will update when I arrive at my desk. I’ll leave a link to the library I was referring to.</p></pre>itsmontoya: <pre><p>Anything with TLS, you&#39;re going to suffer greatly with performance. </p></pre>mwholt: <pre><p>[citation needed]</p> <p><a href="https://istlsfastyet.com/" rel="nofollow">https://istlsfastyet.com/</a></p></pre>jamesog: <pre><p>Go crypto isn&#39;t optimised for ARM yet.</p> <p>See the &#34;Go crypto&#34; section in <a href="https://blog.cloudflare.com/arm-takes-wing/" rel="nofollow">https://blog.cloudflare.com/arm-takes-wing/</a></p></pre>