Quite fast if you use an AOT compiler.
On the server side, it is usually doesn't matter that much. And when it does, there are JVMs that cache JITed code.
I recently saw a small server go from 3 seconds startup on my PC to 4 minutes on a Raspberry.
http://benchmarksgame.alioth.debian.org/u64q/benchmark.php?t...
And Java uses a lot more memory, which is what the article was talking about adversely impacting execution speed.
You know, if the turtle was disqualified ahead of time.
Now let's compare how many lines it takes to read in 2 csvs into structs, sort them by their normals and write their vector products out into a new file. I bet java will do < 100 lines and go will be 10 files and > 1000 lines. It'd be about as honest.
Wouldn't that depend on the program?
For a tiny program (meteor contest) that only needs a fraction of a second on a 6 year old quad-core desktop, maybe 99%
For a tiny program (nbody) that needs a few tens of seconds on the same machine, maybe 0.4%