|author||namusyaka <firstname.lastname@example.org>||Wed Jan 03 05:26:34 2018 +0900|
|committer||Austin Clements <email@example.com>||Wed Jan 03 20:00:20 2018 +0000|
benchstat: specify meta charset=utf-8 to avoid garbled text This commit fixes a few parts that do not conform to the specification of html5 by specifying doctype and html, head, body and title elements. Fixes golang/go#23308 Change-Id: If9e58b056247fce4505c2482443043f9853af3a4 Reviewed-on: https://go-review.googlesource.com/85796 Run-TryBot: Austin Clements <firstname.lastname@example.org> TryBot-Result: Gobot Gobot <email@example.com> Reviewed-by: Austin Clements <firstname.lastname@example.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. You can also manually git clone the repository to
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.