It shouldn't really be surprising. Go and Java share the use of interfaces, but Go's concurrency is far lighter weight, and on top, Java has the extra burden of a virtual machine before it actually hits the CPU as binary code. I suspect also that the Go version could handle a much greater level of concurrency and then the advantage of compilation would be more visible.
On Thursday, 28 February 2019 18:05:55 UTC+1, Isaac Gouy wrote: > > "We reimplemented elPrep in all three languages and benchmarked their > runtime performance and memory use. Results: *The Go implementation > performs best*, yielding the best balance between runtime performance and > memory use. While the Java benchmarks report a somewhat faster runtime than > the Go benchmarks, the memory use of the Java runs is significantly higher." > > proggit discussion > <https://www.reddit.com/r/programming/comments/avsfc6/performance_comparison_of_go_c_and_java_for/> > > article <https://doi.org/10.1101/558056> > > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
