commit | ecb187b06eb016056283eaea1f0a2262f5921572 | [log] [tgz] |
---|---|---|
author | Andrew Bonventre <andybons@golang.org> | Thu Aug 22 20:53:08 2019 -0400 |
committer | Andrew Bonventre <andybons@golang.org> | Fri Aug 23 17:22:24 2019 +0000 |
tree | 08516bfb4f11c086efc7d62ba493c0d8ee1a7378 | |
parent | f6bfb0e03e159cf0a216e60638dcb34c3d5f7298 [diff] |
storage/appengine: update CloudSQL connection string Connections are handled slightly differently in the go111 runtime. Change-Id: I289c3333db2e1b164198bea999c8b085f72618c1 Reviewed-on: https://go-review.googlesource.com/c/perf/+/191478 Reviewed-by: Katie Hockman <katie@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.