Compare the performance of Java 6 -server programs against some other language implementation.
For more information about the Java implementation we measured see ↓ about Java 6 -server.
Java 6 -server comparison summary
| 1/2 1/3 1/4 … Java 6 -server is better | ||||
|---|---|---|---|---|
| Programs | Time | Memory Use | Source Size | Reduced N |
| chameneos-redux | ||||
| regex-dna | 1/2 | 4 | 1/2 | |
| sum-file | ± | 2 | ± | |
| nsieve | ± | 2 | ± | |
| pidigits | ± | 4 | ± | |
| binary-trees | ± | 3 | ± | |
| fannkuch | ± | 3 | ± | |
| spectral-norm | 2 | 9 | ± | |
| fasta | 2 | 3 | ± | |
| nsieve-bits | 2 | 4 | ± | |
| k-nucleotide | 2 | 7 | ± | |
| n-body | 2 | 12 | ± | |
| mandelbrot | 2 | 3 | ± | |
| partial-sums | 4 | 3 | ± | |
| recursive | 4 | 12 | ± | 7 |
| reverse-complement | 6 | 4 | ± | |
± look at the measurements
Java 6 -server comparison measurements
about Java 6 -server
Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode)
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
