A year with Go - Hackdot

Re:A year with Go by nkozyra on Friday June 05, 2015 @10:09PM (#9669309)

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

Keep in mind this is comparing Go 1.4, I'd expect 1.5 to do better.

[ Parent | on HN ]

Re:A year with Go by TheDong on Saturday June 06, 2015 @12:06AM (#9669614)

You 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

[ Parent | on HN ]

Re:A year with Go by pcwalton on Saturday June 06, 2015 @01:02PM (#9671443)

Note 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.

[ Parent | on HN ]

Re:A year with Go by igouy on Saturday June 06, 2015 @08:08PM (#9672838)

JVM 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

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-conclus...

[ Parent | on HN ]

Re:A year with Go by igouy on Friday June 05, 2015 @11:09PM (#9669462)

Keep in mind Go 1.5 has not been released yet :-)

[ Parent | on HN ]