3 ms·
It's fast at compiling, and it's decent-to-fast in performance. It doesn't have the best performance for a compiled language, though. That was an explicit trade
by Jtsummers 4y ago
It's fast at compiling, and it's decent-to-fast in performance. It doesn't have the best performance for a compiled language, though. That was an explicit tradeoff that the Go team made. Getting better performance requires implementing more compiler optimizations, which would slow down compilation. And compiler slowdowns are treated as regressions. Speed has improved though, over the years. [0]
1.17 saw a major performance boost because of the switch from stack-based to register-based ABI for go function calls [1]. The release notes claimed a 5% average improvement, but benhoyt (in that discussion) has benchmarks showing much greater improvement for GoAWK.
[0] https://go.dev/doc/faq#Why_doesnt_Go_have_feature_X https://go.dev/doc/faq#Why_doesnt_Go_have_feature_X
[1] https://news.ycombinator.com/item?id=28201732 https://news.ycombinator.com/item?id=28201732