aboutsummaryrefslogtreecommitdiff
path: root/CONTRIBUTORS
diff options
context:
space:
mode:
authorOri Livneh <ori.livneh@gmail.com>2018-07-09 00:17:44 -0400
committerOri Livneh <ori.livneh@gmail.com>2018-07-09 10:51:08 -0400
commitda9ec3dfca2a1266c4f35cc3d340f094cd71487a (patch)
treef436721ff2c7a1eaced08046ade38cbada9c628e /CONTRIBUTORS
parent1f35fa4aa71bffb5e5672f7ca876561d6adef4fd (diff)
downloadgoogle-benchmark-da9ec3dfca2a1266c4f35cc3d340f094cd71487a.tar.gz
Include system load average in console and JSON reports
High system load can skew benchmark results. By including system load averages in the library's output, we help users identify a potential issue in the quality of their measurements, and thus assist them in producing better (more reproducible) results. I got the idea for this from Brendan Gregg's checklist for benchmark accuracy (http://www.brendangregg.com/blog/2018-06-30/benchmarking-checklist.html).
Diffstat (limited to 'CONTRIBUTORS')
0 files changed, 0 insertions, 0 deletions