|author||Russ Cox <firstname.lastname@example.org>||Fri Jul 22 11:10:43 2022 -0400|
|committer||Russ Cox <email@example.com>||Fri Jul 22 15:52:40 2022 +0000|
A+C: delete AUTHORS and CONTRIBUTORS In 2009, Google's open-source lawyers asked us to create the AUTHORS file to define "The Go Authors", and the CONTRIBUTORS file was in keeping with open source best practices of the time. Re-reviewing our repos now in 2022, the open-source lawyers are comfortable with source control history taking the place of the AUTHORS file, and most open source projects no longer maintain CONTRIBUTORS files. To ease maintenance, remove AUTHORS and CONTRIBUTORS from all repos. For #53961. Change-Id: I7342782a439186dced2e494d70eb254cd6287121 Reviewed-on: https://go-review.googlesource.com/c/perf/+/418901 Run-TryBot: Russ Cox <firstname.lastname@example.org> Reviewed-by: David Chase <email@example.com> TryBot-Result: Gopher Robot <firstname.lastname@example.org>
This subrepository contains command-line tools for analyzing benchmark result data.
cmd/benchstat computes statistical summaries and A/B comparisons of Go benchmarks.
To install all of these commands, run
go install golang.org/x/perf/cmd/...@latest. You can also
git clone https://go.googlesource.com/perf and run
go install ./cmd/... in the checkout.
Underlying the above tools are several packages for working with benchmark data. These are designed to work together, but can also be used independently.
benchfmt reads and writes the Go benchmark format.
benchunit manipulates benchmark units and formats numbers in those units.
benchproc provides tools for filtering, grouping, and sorting benchmark results.
benchmath provides tools for computing statistics over distributions of benchmark measurements.
The following packages are deprecated and no longer supported:
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.
The main issue tracker for the perf repository is located at https://github.com/golang/go/issues. Prefix your issue with “x/perf:” in the subject line, so it is easy to find.