benchproc: remove unnecessary fmt.Sprintf

Change-Id: I88a67c499ba175b5d34f562d40e0abc2b0e87c4e
GitHub-Last-Rev: 9f031f6288a9b535c5eef93e44c5ff94baa1e936
GitHub-Pull-Request: golang/perf#10
Reviewed-by: qiu laidongfeng2 <>
LUCI-TryBot-Result: Go LUCI <>
Reviewed-by: Cherry Mui <>
Reviewed-by: Ian Lance Taylor <>
Auto-Submit: Ian Lance Taylor <>
1 file changed
tree: 013c4b0d87d5e630bfe6ccfa91d8e3decd6d47cd
  1. analysis/
  2. benchfmt/
  3. benchmath/
  4. benchproc/
  5. benchseries/
  6. benchstat/
  7. benchunit/
  8. cmd/
  9. internal/
  10. storage/
  12. go.mod
  13. go.sum

Go benchmark analysis tools

Go Reference

This subrepository holds tools and packages for analyzing Go benchmark results, such as the output of testing package benchmarks.


This subrepository contains command-line tools for analyzing benchmark result data.

cmd/benchstat computes statistical summaries and A/B comparisons of Go benchmarks.

cmd/benchfilter filters the contents of benchmark result files.

cmd/benchsave publishes benchmark results to

To install all of these commands, run go install You can also git clone and run go install ./cmd/... in the checkout.


Underlying the above tools are several packages for working with benchmark data. These are designed to work together, but can also be used independently.

benchfmt reads and writes the Go benchmark format.

benchunit manipulates benchmark units and formats numbers in those units.

benchproc provides tools for filtering, grouping, and sorting benchmark results.

benchmath provides tools for computing statistics over distributions of benchmark measurements.

Deprecated packages

The following packages are deprecated and no longer supported:

storage contains a deprecated version of the benchmark result storage system. These packages have moved to

analysis contains a deprecated version of the benchmark result analysis system. These packages have moved to

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the perf repository is located at Prefix your issue with “x/perf:” in the subject line, so it is easy to find.