3 ms·
As always, it depends on what you're measuring. I find it to be largely a wash http://benchmarksgame.alioth.debian.org/u64q/go.html http://benchmarksgame.alio
by nkozyra 11y ago
As always, it depends on what you're measuring. I find it to be largely a wash
http://benchmarksgame.alioth.debian.org/u64q/go.html http://benchmarksgame.alioth.debian.org/u64q/go.html
Keep in mind this is comparing Go 1.4, I'd expect 1.5 to do better.
- igouy 11y agoKeep in mind Go 1.5 has not been released yet :-)
- TheDong 11y agoYou say that, but because 1.5 is written in Go, it actually does significantly worse on some benchmarks and actual programs. See: https://talks.golang.org/2015/state-of-go-may.slide#11 https://talks.golang.org/2015/state-of-go-may.slide#11
- pcwalton 11y agoNote that the benchmarks game is going to count compile time against Java, but not against Go, since Go is AOT compiled and Java is JIT'd. If your app is a long-running server, you should take the benchmarks game numbers with a grain of salt.
- igouy 11y agoJVM start-up, JIT, OSR etc take very little time relative to most of the workloads shown on the benchmarks game. http://benchmarksgame.alioth.debian.org/play.html#java http://benchmarksgame.alioth.debian.org/play.html#java The notable exception (not included in summary measurements) is the few tenths of a second run-time for meteor-contest. Of that few tenths of a second: JVM startup takes 95%, JIT and OSR another 4.9%. Whatever kind-of app you have, you should take general statements about program performance with a grain of salt, there's even a page for that -- http://benchmarksgame.alioth.debian.org/dont-jump-to-conclusions.html http://benchmarksgame.alioth.debian.org/dont-jump-to-conclus...