go
/
build
зеркало из https://github.com/golang/build.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
build/perf
История
Michael Anthony Knyszek 16a1c3d308 perf: update the default benchmarks' suffixes from -8 to -16 
We moved from 8 core machines for performance tests recently to 16
core machines. Some of the benchmark names changed as a result. This
change updates those benchmarks that appear on the landing page.

Change-Id: If8964aff3491da3a5dd7d75d1ea7a9ab12365e88
Reviewed-on: https://go-review.googlesource.com/c/build/+/570239
Reviewed-by: Michael Pratt <mpratt@google.com>
Reviewed-by: David Chase <drchase@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
 		2024-03-11 16:22:00 +00:00
..
app perf: update the default benchmarks' suffixes from -8 to -16 2024-03-11 16:22:00 +00:00
Dockerfile all: use Go 1.21 for building services 2024-01-17 23:47:09 +00:00
Makefile perf: add CA certificates to container 2022-04-12 17:45:55 +00:00
README.md perf: update docs with influx testing instructions 2022-11-16 23:07:30 +00:00
deployment-prod.yaml all: make copyright headers consistent 2023-03-01 01:31:01 +00:00
main.go all: make copyright headers consistent 2023-03-01 01:31:01 +00:00

README.md

Performance analysis system

This package contains the https://perf.golang.org/ benchmark result analysis system. It serves as a front-end to the benchmark result storage system at https://perfdata.golang.org/.

The storage system is designed to have a standardized REST API at https://perfdata.golang.org/, and we encourage additional analysis tools to be written against the API. An example client can be found in the perfdata package.

Local

Both storage and analysis can be run locally; the following commands will run the complete stack on your machine with an in-memory datastore.

To run the storage system:

$ go install golang.org/x/build/perfdata/localperfdata@latest
$ localperfdata -addr=:8081 -view_url_base=http://localhost:8080/search?q=upload: &

To run the analysis frontend:

$ make docker-prod
$ docker run --rm --net=host gcr.io/symbolic-datum-552/perf:latest -listen-http=:8080 -perfdata=http://localhost:8081

Browse to https://localhost:8080 (note that the instance uses a self-signed certificate).

To run the analysis frontend connected to a local InfluxDB instance, first follow the instructions to set one up. Then, run the above command but with the -influx-host and -influx-token flags set to their appropriate values (as specified by the InfluxDB setup instructions).

Send an HTTP request to https://localhost:8080/cron/sync-influx to sync the local instances together.

Google Cloud

One-time setup:

  1. IAM setup, based on https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity#authenticating_to:

a. Create GCP service account:

$ gcloud iam service-accounts create perf-prod \
    --description="Runs golang.org/x/build/perf"

c. Allow Kubernetes service account (created by deployment-prod.yaml) to impersonate the GCP service account:

$ gcloud iam service-accounts add-iam-policy-binding \
    perf-prod@<PROJECT>.iam.gserviceaccount.com \
    --role roles/iam.workloadIdentityUser \
    --member "serviceAccount:<PROJECT>.svc.id.goog[prod/perf-prod]"

Deployment

See the documentation on deployment.