3 ms·

'Modern JVMs can make on the fly optimizations based on the runtime profile' That's something I've heard ever since hotspot came out, but it's not a silver bul

'Modern JVMs can make on the fly optimizations based on the runtime profile' That's something I've heard ever since hotspot came out, but it's not a silver bullet to beating C/C++ etc. Here are some server tests. Some are comparable, some are definitely not: http://shootout.alioth.debian.org/u64q/java.php http://shootout.alioth.debian.org/u64q/java.php

jbellis 17y ago
"Sometimes no-warmup is important (see comments above about pacemakers), but more often a short warmup period is irrelevant to the overall application. If I'm using an IDE, I expect a largish loading period... but then I'm using the IDE all day. I don't use an IDE for 0.1 sec. If warmup is NOT important to the application, then allow the JVM a warmup period before comparing performance numbers. Many of the benchmarks in the language shootout at http://shootout.alioth.debian.org http://shootout.alioth.debian.org fall into this camp: too short to measure something interesting. Nearly all complete in 1 minute or less." http://blogs.azulsystems.com/cliff/2009/09/java-vs-c-performance-again.html http://blogs.azulsystems.com/cliff/2009/09/java-vs-c-perform...
- igouy 17y ago
  The replies I post never seem to appear on that blog so here they are: http://www.reddit.com/r/programming/comments/9ic0x/java_vs_c_performance_again/c0d1qxr http://www.reddit.com/r/programming/comments/9ic0x/java_vs_c... And measurements: http://shootout.alioth.debian.org/help.php#java http://shootout.alioth.debian.org/help.php#java
fauigerzigerk 17y ago
What you link to are tests using the server VM but without warmup. You need to select "Java 6 steady-state" to get the warmup. [Edit] Actually the state-state one averages over multiples restarts including JITed and non-JITed runs.
- igouy 17y ago
  See how little difference that "warmup" makes for these tiny programs - with the obvious exception of the binary-trees program - http://shootout.alioth.debian.org/help.php#java http://shootout.alioth.debian.org/help.php#java

jbellis 17y ago

"Sometimes no-warmup is important (see comments above about pacemakers), but more often a short warmup period is irrelevant to the overall application. If I'm using an IDE, I expect a largish loading period... but then I'm using the IDE all day. I don't use an IDE for 0.1 sec. If warmup is NOT important to the application, then allow the JVM a warmup period before comparing performance numbers. Many of the benchmarks in the language shootout at http://shootout.alioth.debian.org http://shootout.alioth.debian.org fall into this camp: too short to measure something interesting. Nearly all complete in 1 minute or less." http://blogs.azulsystems.com/cliff/2009/09/java-vs-c-performance-again.html http://blogs.azulsystems.com/cliff/2009/09/java-vs-c-perform...

igouy 17y ago
The replies I post never seem to appear on that blog so here they are: http://www.reddit.com/r/programming/comments/9ic0x/java_vs_c_performance_again/c0d1qxr http://www.reddit.com/r/programming/comments/9ic0x/java_vs_c... And measurements: http://shootout.alioth.debian.org/help.php#java http://shootout.alioth.debian.org/help.php#java

fauigerzigerk 17y ago

What you link to are tests using the server VM but without warmup. You need to select "Java 6 steady-state" to get the warmup. [Edit] Actually the state-state one averages over multiples restarts including JITed and non-JITed runs.

igouy 17y ago
See how little difference that "warmup" makes for these tiny programs - with the obvious exception of the binary-trees program - http://shootout.alioth.debian.org/help.php#java http://shootout.alioth.debian.org/help.php#java