That's one. However, many of the benchmarks on that page are skewed towards scientific computing (scimark, linpack, Erathostene's Sieve, parts of SPECjvm98), which is probably not the most common use of Java. The last (specjvm98) is an old - but admittedly valid - client side benchmark. We know that JRockit does not excel at floating point, and it is one area we are looking at for future optimizations.
Other public benchmarks, with more of a server-side focus are SPECjbb and SPECjAPP. The former puts most emphasis on memory management. There is a recent result published on JRockit here
, as well as a full list of results here
. When we run head-to-head comparisons vs Sun Hotspot, we see that JRockit generally outperforms Hotspot by a significant amount on an otherwise identical setup. Of course, I encourage those of you who have access to this benchmark to verify this yourselves.
SPECjAPP is designed to benchmark an application server, so it does not directly measure the JVM. If you have the benchmark, you can however run identical setups and switch the JVM only. I wouldn't be surprised if you got good results with JRockit.
Common reports from customers who have switched from Sun Hotspot to JRockit is everything from no change to twice as fast. This is generally on larger server applciations, where JRockit self-tuning and runtime optimization is given time adapt itself to the application.
At the end of the day, the only benchmark really worth its salt is your own application. Try out JRockit with your app - it's free to use - and let us know the results!
Oh, and if you have a benchmark that runs poorly with JRockit, post it to our newsgroup
. Chances are we will fix your issue, such as in this example