|author||Bryan C. Mills <firstname.lastname@example.org>||Thu Dec 03 13:19:11 2020 -0500|
|committer||Bryan C. Mills <email@example.com>||Thu Dec 03 21:05:31 2020 +0000|
go.mod: upgrade go-sqlite3 to latest If I am following correctly, this should pull in the fix for mattn/go-sqlite3#867. For #42941 Change-Id: Ic9360e629d9dc21f714b75806d30abe9a3f24123 Reviewed-on: https://go-review.googlesource.com/c/perf/+/275192 Trust: Bryan C. Mills <firstname.lastname@example.org> Run-TryBot: Bryan C. Mills <email@example.com> TryBot-Result: Go Bot <firstname.lastname@example.org> Reviewed-by: Dmitri Shuralyov <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 golang.org/x/perf/cmd/.... You can also manually git clone the repository and run
go install ./cmd/....
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.