Secondary metrics representation

[Aleksey Shipilev]

Hi Bernd,

On 04/18/2015 02:11 AM, Bernd Eckenfels wrote:
> However I have some hard time to "read" the following representation:
> 
> Secondary result "·gc.time":
>   1144,000 ±(99.9%) 0,001 ms [Sum]
>   (min, avg, max) = (189,000, 286,000, 499,000), stdev = 143,937
>   CI (99.9%): [1144,000, 1144,000] (assumes normal distribution)
> 
> The avg. runtime is 286ms. I wonder why the error and CI is based on
> the Sum? And where is the pretty narrow CI coming from when min and max
> varry that much?

The "gc.time" metric value and CI are calculated as the sum over the
values from all iterations, and this time adds up to 1144ms. (min, avg,
max) is calculated over the same set values from each iteration. So,
286ms is the average gc.time across iterations.

We might just want to drop (min, avg, max) for the metrics that
aggregate to a sum/max. Other formatting suggestions are welcome.

Thanks,
-Aleksey