Java 6 -server measurements

This table shows 4 measurements - CPU Time, Elapsed Time, Memory and Code.

Each row shows those measurements for a particular Java 6 -server program with a particular command-line input value N.

This table shows all the accepted Java 6 -server programs.

Program Source Code  N  CPU secs Elapsed secs Memory KB Code B
binary-trees  #2  120.3110,228603
binary-trees  #2  141.0419,368603
binary-trees  #2  166.8926,808603
chameneos-redux   60,0000.6812,7601462
chameneos-redux   600,0003.6912,5201462
chameneos-redux   6,000,00034.7412,3081462
chameneos-redux  #2  60,0000.4612,0721429
chameneos-redux  #2  600,0002.0412,0681429
chameneos-redux  #2  6,000,00017.5112,0921429
fannkuch  #2  101.128,776761
fannkuch  #2  1111.478,804761
fannkuch  #2  90.3010,880761
fannkuch  #4  101.068,896555
fannkuch  #4  1111.058,884555
fannkuch  #4  90.288,872555
fasta  #2  250,0000.429,0801240
fasta  #2  2,500,0002.389,1561240
fasta  #2  25,000,00021.469,1841240
startup   10.14 112
startup   20017.07 112
k-nucleotide   10,0000.9522,1921052
k-nucleotide   100,0003.1038,3561052
k-nucleotide   1,000,00015.8970,9641052
mandelbrot   1200.185,040665
mandelbrot   3,0003.2511,044665
mandelbrot   6000.3110,896665
mandelbrot  #3  1200.203,548623
mandelbrot  #3  3,0003.2411,092623
mandelbrot  #3  6000.3310,944623
meteor-contest   2,0981.5512,0564368
meteor-contest  #2  2,0980.7912,7565177
n-body   200,0000.3812,0001430
n-body   2,000,0001.8112,0081430
n-body   20,000,00015.9312,0121430
n-body  #2  200,0000.3511,5161424
n-body  #2  2,000,0001.6711,5401424
n-body  #2  20,000,00014.7511,5241424
nsieve   70.599,832452
nsieve   81.1411,088452
nsieve   92.2918,856452
nsieve  #3  70.5811,868296
nsieve  #3  81.1313,132296
nsieve  #3  92.2520,592296
nsieve-bits   103.799,984478
nsieve-bits   118.3211,248478
nsieve-bits   91.669,368478
nsieve-bits  #2  103.2018,872701
nsieve-bits  #2  117.1123,900701
nsieve-bits  #2  91.3111,120701
nsieve-bits  #3  103.1312,080517
nsieve-bits  #3  117.0813,344517
nsieve-bits  #3  91.3111,456517
nsieve-bits  #4  102.3212,084523
nsieve-bits  #4  115.0413,364523
nsieve-bits  #4  91.0611,480523
nsieve-bits  #5  102.8312,172423
nsieve-bits  #5  116.4113,412423
nsieve-bits  #5  91.1511,516423
partial-sums  #2  25,0000.2810,956470
partial-sums  #2  250,0000.998,480470
partial-sums  #2  2,500,00011.4410,964470
partial-sums  #3  25,0000.2510,960474
partial-sums  #3  250,0000.768,484474
partial-sums  #3  2,500,0009.158,488474
pidigits   1,5004.3115,812800
pidigits   2,50010.9015,820800
pidigits   5001.1815,720800
pidigits  #2  1,5000.798,912938
pidigits  #2  2,5001.928,992938
pidigits  #2  5000.238,720938
recursive   116.7612,044427
recursive   30.214,116427
recursive   70.4811,628427
regex-dna  #4  100,0002.3735,808921
regex-dna  #4  300,0005.1658,124921
regex-dna  #4  500,0007.8175,892921
reverse-complement  #4  25,0000.223,984592
reverse-complement  #4  250,0000.3611,472592
reverse-complement  #4  2,500,0001.3058,932592
spectral-norm   3,0007.309,648514
spectral-norm   5000.429,156514
spectral-norm   5,50024.0110,008514
sum-file   1,0000.6610,576265
sum-file   11,0004.1510,832265
sum-file   21,0007.5410,944265
sum-file  #4  1,0000.439,960226
sum-file  #4  11,0002.269,960226
sum-file  #4  21,0004.109,972226
thread-ring   100,0004.4225,340587
thread-ring   1,000,00035.8325,368587
thread-ring   10,000,000348.6025,364587
thread-ring  #3  100,0001.9223,348530
thread-ring  #3  1,000,00014.4223,340530
thread-ring  #3  10,000,000134.9823,336530

 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

  Home   Flawed   Fastest   License   Help