commit | 151b6387e3f2aa5908e4a6074f06be9ecc34f004 | [log] [tgz] |
---|---|---|
author | Elias Naur <mail@eliasnaur.com> | Wed Mar 06 10:20:39 2019 +0100 |
committer | Elias Naur <mail@eliasnaur.com> | Wed Mar 06 14:40:31 2019 +0000 |
tree | 08c2fe8dd95473083312ee568174bd769a602d3d | |
parent | 844a5f5b46f41e1c8506d833252f15cbff329d23 [diff] |
benchstat: skip test on GOOS=android Change-Id: Ib5180af43a22168e57b94deec2cd37b980365ab0 Reviewed-on: https://go-review.googlesource.com/c/perf/+/165697 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.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.
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.