6 ms·
> When the author made the claim that Java was as fast as Go, I was a bit surprised. I wasn't aware Go had caught up to Java. As a Go "fan": it hasn't. It's cl
by elithrar 13y ago
> When the author made the claim that Java was as fast as Go, I was a bit surprised. I wasn't aware Go had caught up to Java.
As a Go "fan": it hasn't. It's close in some things, faster in a few, but the JVM has years (and years) of performance tuning in it, and Go won't unequivocally beat Java for some time (if ever).
(This WiFi connection is failing me right now, but there's a good number of Go vs. Java benchmarks out there, for whatever benchmarks are worth)
- eranation 13y agoI was only referring to the Web framework benchmark, where Go (1.1 I think) is taking the lead over Servlets on many of the benchmarks. Still impressive.
- deleted 13y ago[deleted]
- nemothekid 13y agoThat was my reaction as well. We are using Go in production here and I'm very much a Go fan, but I'd be surprised if Go caught up to Java in so little time.
- eranation 13y agoI was referring to this benchmark: http://www.techempower.com/benchmarks/ http://www.techempower.com/benchmarks/
- continuations 13y agoThat benchmark makes it clear Go has not caught up to Java in performance. Out of the 10 tests that have both Java and Go results, Java is faster than Go in 9 tests while Go is faster than Java in 1 test (by 0.2%, so not significant).
- eranation 13y agoI counted go lead on 3 of the tests, but I agree with your point, will fix the article accordingly, thanks!
- continuations 13y agoOnly 1 of those 3 tests (the very 1st one) also contains Java results. The other 2 are Windows tests that don't contain any Java results. Hence I said that out of the 10 tests that contain both Go and Java results Go only beats Java (by a statistically insignificant 0.2%) in 1 test while Java beats Go in the other 9 tests.
- eranation 13y agoYou are so right, bad attention to details day for me. corrected the article in any case. thanks!
- rieter 13y agoThere is no reason why Go can't quickly catch up with Java. It's memory model is better suited to optimization vs. JVM.