"Nice" report for failed forks/benchmarks

Vladimir Sitnikov sitnikov.vladimir at gmail.com
Tue Jun 2 18:49:04 UTC 2015


Hi,

I happen to test some finalizer performance, and it looks like jmh's
report is not very nice there.
Does anybody have idea how that should be depicted?
I guess it might need some un-biasing in case just a couple of runs
fails. For instance, if 3 of 5 forks survive we would have to average
apples with exceptions somehow.

# Warmup Iteration   4: 202029,343 ns/op
# Warmup Iteration   5: 846066,057 ns/op
# Warmup Iteration   6: <failure>
java.lang.OutOfMemoryError: GC overhead limit exceeded

...

# Run complete. Total time: 00:00:18

Benchmark  Mode  Cnt  Score   Error  Units

-- 
Regards,
Vladimir Sitnikov


More information about the jmh-dev mailing list