Take the benchmarkgames site with a big grain of salt. They're running on an old processor, and that biases results a lot. For example, someone submitted a patc

Take the benchmarkgames site with a big grain of salt. They're running on an old processor, and that biases results a lot. For example, someone submitted a patch that significantly sped up a Java benchmark by using `Math.fma()`. However, because the processor the benchmarks site is running on is old and does not support the underlying instruction that `Math.fma()` uses, it ended up way slower. I ran several benchmarks locally on a CPU that's a few years old where the benchmarks site shows golang being faster than Java, without changing the code, and I got the opposite result (Java was faster). Especially the longer the program ran. For example, the site shows that golang is faster in the spectral norm benchmark. Running it locally with a larger input parameter: golang: time ./test 30000 1.274224153 18.81 real 70.19 user 0.38 sys Java: time java spectralnorm1 30000 1.274224153 16.18 real 105.95 user 0.45 sys Or with the nbody benchmark: golang: time ./nbody 60000000 -0.169075164 -0.169012474 6.09 real 6.04 user 0.02 sys Java: time java nbody 60000000 -0.169075164 -0.169012474 6.04 real 5.94 user 0.06 sys