Step 1 : Are the Java 6 -server programs faster? At a glance.
This chart shows 3 comparisons - Time-used, Memory-used and Code-used ~ speed and size.
Each chart bar shows, for one unidentified benchmark, how much the fastest Java 6 -server program used compared to the fastest OCaml program.
Step 2 : Are the Java 6 -server programs faster? Approximately.
This table shows 3 comparisons - Time-used, Memory-used and Code-used ~ speed and size.
Each table row shows, for one named benchmark, how much the fastest Java 6 -server program used compared to the fastest OCaml program.
| Java 6 -server used what fraction? used how many times more? | ||||
|---|---|---|---|---|
| Benchmark | Time | Memory | Code | |
| n-body | 1/4 | 18× | ± | |
| recursive | 1/2 | 12× | ± | |
| spectral-norm | ± | 8× | ± | |
| fasta | ± | 3× | ± | |
| nsieve | ± | 2× | ± | |
| partial-sums | ± | 19× | ± | |
| mandelbrot | ± | 15× | ± | |
| k-nucleotide | ± | 2× | ± | |
| reverse-complement | ± | ± | ± | |
| nsieve-bits | ± | 7× | 3× | |
| regex-dna | ± | 2× | ± | |
| fannkuch | 3× | 15× | ± | |
| binary-trees | 5× | 3× | ± | |
± read the measurements and then read the program source code.
Step 3 : Are the Java 6 -server programs faster? Measurements.
This table shows 5 measurements - CPU Time, Elapsed Time, Memory, Code and ≈ CPU Load ~ speed and size.
For each named benchmark, measurements of the fastest Java 6 -server program are shown for comparison against measurements of the fastest OCaml program.
| Program Source Code | CPU secs | Elapsed secs | Memory KB | Code B | ≈ CPU Load |
|---|---|---|---|---|---|
| n-body | |||||
| Java 6 -server | 14.75 | 11,524 | 1424 | ||
| OCaml | 54.00 | 644 | 1239 | ||
| recursive | |||||
| Java 6 -server | 0.48 | 11,628 | 427 | ||
| OCaml | 0.92 | 948 | 389 | ||
| spectral-norm | |||||
| Java 6 -server | 24.01 | 10,008 | 514 | ||
| OCaml | 31.63 | 1,196 | 369 | ||
| fasta | |||||
| Java 6 -server | 21.46 | 9,184 | 1240 | ||
| OCaml | 27.89 | 3,280 | 984 | ||
| nsieve | |||||
| Java 6 -server | 2.25 | 20,592 | 296 | ||
| OCaml | 2.16 | 9,380 | 295 | ||
| partial-sums | |||||
| Java 6 -server | 4.88 | 10,648 | 711 | ||
| OCaml | 4.64 | 564 | 508 | ||
| mandelbrot | |||||
| Java 6 -server | 0.33 | 10,944 | 623 | ||
| OCaml | 0.29 | 716 | 444 | ||
| k-nucleotide | |||||
| Java 6 -server | 15.89 | 70,964 | 1052 | ||
| OCaml | 13.83 | 34,636 | 845 | ||
| reverse-complement | |||||
| Java 6 -server | 1.30 | 58,932 | 592 | ||
| OCaml | 1.02 | 47,244 | 540 | ||
| nsieve-bits | |||||
| Java 6 -server | 1.06 | 11,480 | 523 | ||
| OCaml | 0.80 | 1,584 | 176 | ||
| regex-dna | |||||
| Java 6 -server | 7.81 | 75,892 | 921 | ||
| OCaml | 5.54 | 45,364 | 615 | ||
| fannkuch | |||||
| Java 6 -server | 0.28 | 8,872 | 555 | ||
| OCaml | 0.11 | 592 | 485 | ||
| binary-trees | |||||
| Java 6 -server | 6.89 | 26,808 | 603 | ||
| OCaml | 1.44 | 8,844 | 502 | ||
| pidigits | |||||
| Java 6 -server | 0.79 | 8,912 | 938 | ||
| OCaml | |||||
| chameneos-redux | |||||
| Java 6 -server | 0.46 | 12,072 | 1429 | ||
Step 4 : Are there other Java 6 -server programs for these benchmarks?
Remember - those are just the fastest Java 6 -server and OCaml programs measured on this OS/machine. Check if there are other implementations of these benchmark programs for Java 6 -server.
Maybe one of those other Java 6 -server programs is fastest on a different OS/machine.
Step 5 : Are there other faster programs for these benchmarks?
Remember - those are just the fastest Java 6 -server and OCaml programs measured on this OS/machine. Check if there are faster implementations of these benchmark programs for other programming languages.
Maybe one of those other programs is fastest on a different OS/machine.
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