commit | ea1fc7ea91ba64ca9b3d0d016e9627a931b6abf8 | [log] [tgz] |
---|---|---|
author | Brad Fitzpatrick <bradfitz@golang.org> | Wed Jan 10 18:49:31 2018 +0000 |
committer | Brad Fitzpatrick <bradfitz@golang.org> | Wed Jan 10 20:00:12 2018 +0000 |
tree | e07dc7ffbc247af9e33c7699b6c1d3bebdc7d212 | |
parent | f4a8417d34a36fcfae7fb9fe0d8d1e3b2b1ecaa8 [diff] |
storage/app: skip tests on plan9 The whole package was alread marked as +build !plan9, but I missed the tests before. Change-Id: I1f80512e8fbe939709d7159d9ab67c061f3433ba Reviewed-on: https://go-review.googlesource.com/87256 Reviewed-by: David du Colombier <0intro@gmail.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
. 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.