Numbers that small aren't statistically significant. Our J2DBench
benchmark calibrates each test to run a number of iterations that result
in at least 2.5 seconds of run time. Try upping your loop iterations by
a factor of 100 and you'll get numbers with better accuracy and precision...
...jim
Mario Torre wrote:
[neug...@galactica OpenJDKPerformaceTest]$
../openjdk/build/linux-amd64/bin/java -cp build/classes/
net.java.openjdk.Main
warmed up run time in ms: 32
total time in ms: 144
[neug...@galactica OpenJDKPerformaceTest]$
../openjdk-proxy/build/linux-amd64/bin/java -cp build/classes/
net.java.openjdk.Main
warmed up run time in ms: 31
total time in ms: 157
