speed and size Java 6 -server ÷ Python CPython | Computer Language Benchmarks Game

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 Python CPython 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 Python CPython program.

Java 6 -server used what fraction? used how many times more?
Benchmark	Time	Memory	Code
n-body	¹/₁₃₇	5×	±
spectral-norm	¹/₁₃₆	3×	2×
recursive	¹/₄₇	4×	±
nsieve-bits	¹/₃₃	2×	2×
fasta	¹/₃₂	4×	2×
fannkuch	¹/₁₉	4×	±
mandelbrot	¹/₁₇	¹/₃	2×
chameneos-redux	¹/₁₆	5×	2×
binary-trees	¹/₁₀	2×	2×
k-nucleotide	¹/₄	3×	2×
nsieve	¹/₃	¹/₂	±
reverse-complement	¹/₂	±	2×
partial-sums	±	±	±
regex-dna	3×	3×	3×
pidigits	3×	4×	4×

± 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 Python CPython program.

Program Source Code	CPU secs	Memory KB	Code B
n-body
Java 6 -server	14.75	11,524	1424
Python CPython	2,015.78	2,440	1027
spectral-norm
Java 6 -server	24.01	10,008	514
Python CPython	3,261.32	2,900	282
recursive
Java 6 -server	0.48	11,628	427
Python CPython	22.37	3,048	360
nsieve-bits
Java 6 -server	1.06	11,480	523
Python CPython	34.97	4,936	288
fasta
Java 6 -server	21.46	9,184	1240
Python CPython	692.04	2,420	779
fannkuch
Java 6 -server	0.28	8,872	555
Python CPython	5.38	2,404	411
mandelbrot
Java 6 -server	0.33	10,944	623
Python CPython	5.59	29,632	312
chameneos-redux
Java 6 -server	17.51	12,092	1429
Python CPython	275.84	2,576	866
binary-trees
Java 6 -server	6.89	26,808	603
Python CPython	66.96	16,172	377
k-nucleotide
Java 6 -server	15.89	70,964	1052
Python CPython	58.45	25,208	475
nsieve
Java 6 -server	2.25	20,592	296
Python CPython	7.35	42,400	278
reverse-complement
Java 6 -server	1.30	58,932	592
Python CPython	2.73	49,072	288
partial-sums
Java 6 -server	4.88	10,648	711
Python CPython	7.03	12,680	482
regex-dna
Java 6 -server	7.81	75,892	921
Python CPython	2.88	23,000	314
pidigits
Java 6 -server	0.23	8,720	938
Python CPython	0.08	2,164	257

Step 4 : Are there other Java 6 -server programs for these benchmarks?

Remember - those are just the fastest Java 6 -server and Python CPython 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 Python CPython 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