For more information about a Timeout or Error click the program name and scroll-down to the 'build & benchmark results'.

÷

 Java 6 -server measurements

Program & Logs Time secs Memory KB Size B  N 
binary-trees6.8926,808603 16
chameneos-redux17.5112,0921429 6,000,000
fannkuch11.048,884555 11
fasta21.469,1841240 25,000,000
k-nucleotide15.8870,9641052 1,000,000
mandelbrot3.2411,092623 3,000
meteor-contest0.7912,7565177 2,098
n-body14.7511,5241424 20,000,000
nsieve2.2520,592296 9
nsieve-bits5.0413,364523 11
partial-sums9.148,488474 2,500,000
pidigits1.928,992938 2,500
recursive6.7612,044427 11
regex-dna7.8175,892921 500,000
reverse-complement1.3058,932592 2,500,000
spectral-norm24.0110,008514 5,500
startup17.07 112 200
sum-file4.109,972226 21,000
thread-ring134.9823,336530 10,000,000

 Java 6 -server : ubiquitous jit server virtual machine 

java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode, sharing)

Home Page: http://java.sun.com/j2se/

Download: http://java.sun.com/j2se/downloads/

"Remember how HotSpot works. It starts by running your program with an interpreter. When it discovers that some method is "hot" -- that is, executed a lot, either because it is called a lot or because it contains loops that loop a lot -- it sends that method off to be compiled. After that one of two things will happen, either the next time the method is called the compiled version will be invoked (instead of the interpreted version) or the currently long running loop will be replaced, while still running, with the compiled method. The latter is known as "on stack replacement" and exists in the 1.3/1.4 HotSpot based systems."

Benchmarking the Java HotSpot VM

Revised BSD license