benchmark/tools/gbench/Inputs
Roman Lebedev 12dc5eeafc
Statistics: add support for percentage unit in addition to time (#1219)
* Statistics: add support for percentage unit in addition to time

I think, `stddev` statistic is useful, but confusing.

What does it mean if `stddev` of `1ms` is reported?
Is that good or bad? If the `median` is `1s`,
then that means that the measurements are pretty noise-less.

And what about `stddev` of `100ms` is reported?
If the `median` is `1s` - awful, if the `median` is `10s` - good.

And hurray, there is just the statistic that we need:
https://en.wikipedia.org/wiki/Coefficient_of_variation

But, naturally, that produces a value in percents,
but the statistics are currently hardcoded to produce time.

So this refactors thinkgs a bit, and allows a percentage unit for statistics.

I'm not sure whether or not `benchmark` would be okay
with adding this `RSD` statistic by default,
but regales, that is a separate patch.

Refs. https://github.com/google/benchmark/issues/1146

* Address review notes
2021-09-03 15:36:56 +01:00
..
test1_run1.json [Tooling] report.py: whoops, don't ignore the rest of benches after a bad one. 2019-03-06 18:13:22 +03:00
test1_run2.json [Tooling] report.py: whoops, don't ignore the rest of benches after a bad one. 2019-03-06 18:13:22 +03:00
test2_run.json [Tools] A new, more versatile benchmark output compare tool (#474) 2017-11-07 13:35:25 -08:00
test3_run0.json [Tooling] Rewrite generate_difference_report(). (#678) 2018-09-19 15:59:13 +03:00
test3_run1.json [Tooling] Rewrite generate_difference_report(). (#678) 2018-09-19 15:59:13 +03:00
test4_run0.json Statistics: add support for percentage unit in addition to time (#1219) 2021-09-03 15:36:56 +01:00
test4_run1.json Statistics: add support for percentage unit in addition to time (#1219) 2021-09-03 15:36:56 +01:00
test4_run.json compare.py: sort the results (#1168) 2021-06-03 16:22:52 +03:00