| commit | 6e6d33e29852650cab301f4dbeac9b7d67c6d542 | [log] [tgz] |
|---|---|---|
| author | Gabriel Aszalos <gabriel.aszalos@gmail.com> | Mon Dec 18 16:01:51 2017 +0100 |
| committer | Daniel Martà <mvdan@mvdan.cc> | Wed Jul 04 12:45:30 2018 +0000 |
| tree | 78a68b49c19b1e4069e24b1935d7a652de06519e | |
| parent | 3d766fafb1660c8f310d56a47efb499b1240d759 [diff] |
README: correct installation instructions Fixes golang/go#23167 Change-Id: I04e9f92fd0fc83f1f489e9f2a328c4916c06b8e6 Reviewed-on: https://go-review.googlesource.com/84595 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Daniel Martà <mvdan@mvdan.cc>
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 $GOPATH/src/golang.org/x/perf.
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.