It's odd that J2DBench showed a difference since nothing you did should
have affected those benchmarks. I don't think it has any benchmark
which shows the impact of a pipeline validation, so your standalone test
is the only one that I think addresses the issue.
Rather than setting up a machin
Il 15/07/2009 23:41, Jim Graham ha scritto:
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 wi
