|author||Brad Fitzpatrick <email@example.com>||Wed May 01 03:06:09 2019 +0000|
|committer||Brad Fitzpatrick <firstname.lastname@example.org>||Wed May 01 05:18:39 2019 +0000|
storage: require cgo, not !plan9 I previously added !plan9 build tags to fix the build on plan9, but this didn't fix other ports where sqlite3 wasn't available. What I really wanted was to require cgo. This "fixes" the build for e.g. linux/ppc64. Change-Id: I2fd6e824f358ca0e3534458b3b8d900756de4bbe Reviewed-on: https://go-review.googlesource.com/c/perf/+/174678 Run-TryBot: Brad Fitzpatrick <email@example.com> TryBot-Result: Gobot Gobot <firstname.lastname@example.org> Reviewed-by: Ian Lance Taylor <email@example.com>
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.
storage contains the https://perfdata.golang.org/ benchmark result storage system.
analysis contains the https://perf.golang.org/ benchmark result analysis system.
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
The storage system is designed to have a standardized API, and we encourage additional analysis tools to be written against the API. A client can be found in the storage package.
The easiest way to install is to run
go get -u golang.org/x/perf/cmd/.... You can also manually git clone the repository to
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.