Performance measurement, storage, and analysis.

Clone this repo:

Branches

  1. 03971e3 README.md: update for Go module-based build by Michael Pratt · 4 weeks ago master
  2. 40a54f1 all: go fmt ./... by Russ Cox · 8 months ago
  3. bdcc622 README.md: add badge to pkg.go.dev by Julie Qiu · 11 months ago
  4. 3748ef0 go.mod: upgrade go-sqlite3 to latest by Bryan C. Mills · 11 months ago
  5. d949658 vendor: delete by Dmitri Shuralyov · 1 year, 8 months ago

Go performance measurement, storage, and analysis tools

Go Reference

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 install golang.org/x/perf/storage/localperfdata@latest
go install golang.org/x/perf/analysis/localperf@latest
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.

Download/Install

The easiest way to install is to run go install golang.org/x/perf/cmd/...@latest. You can also manually git clone the repository and run go install golang.org/x/perf/cmd/....

Report Issues / Send Patches

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.