|author||Josh Bleecher Snyder <firstname.lastname@example.org>||Thu May 25 06:50:59 2017 -0700|
|committer||Josh Bleecher Snyder <email@example.com>||Sat May 27 01:32:33 2017 +0000|
benchstat: don't print sign for 0% when there is no change When all samples are identical, instead of printing +0.00%, print just 0.00%. This is not just more accurate. When benchmarking the compiler, one item of interest is the impact on object file and executable sizes. These can change by tiny amounts, below two sig figs. However, the existence of any change is sometimes a cue to the reader to investigate further. This obviously should not be relied on, but it is nevertheless a useful signal. Change-Id: I1e5157a52fc47c6871ca87b0e9cff223f4fd43d9 Reviewed-on: https://go-review.googlesource.com/44190 Run-TryBot: Josh Bleecher Snyder <firstname.lastname@example.org> TryBot-Result: Gobot Gobot <email@example.com> Reviewed-by: Brad Fitzpatrick <firstname.lastname@example.org>
This subrepository holds the source for various packages and tools related to performance measurement, storage, and analysis.
cmd/benchstat contains a command-line tool that computes and compares statistics about benchmarks.
cmd/benchsave contains a command-line tool for publishing benchmark results.
Both storage and analysis can be run locally; the following commands will run the complete stack on your machine with an in-memory datastore.
go get -u golang.org/x/perf/storage/localperfdata go get -u golang.org/x/perf/analysis/localperf localperfdata -addr=:8081 -view_url_base=http://localhost:8080/search?q=upload: & localperf -addr=:8080 -storage=http://localhost:8081
Contributions to Go are appreciated. See http://golang.org/doc/contribute.html.