From today you can now
prepare and run custom prombench benchmarks from any Prometheus PR (
docs,
design). The goal is to increase the community productivity by giving more efficiency data on the various Prometheus features we work on.
It's enabled by the two new
/prombench command flags allowing alternative branch/commit (
--bench.version) or directory (
--bench.directory) with
the manifests and nodepool configurations to use for the benchmark deployments.
Example flow (2 steps):1. Create a custom benchmark scenario on a new test-infra branch. Only maintainers can push those, but we welcome contributors to propose those via PRs. For example
bench/nhcbconvert2. From a
Prometheus PR run
/prombench <version to cmp with> --bench.version=bench/nhcbconvert . Only maintainers can do that, so
if you're not in maintainer, feel free to ask for it on your PR, if you want to trigger one. Prombench should confirm the benchmark as usual, but this time with more links:

A. Shows you exact configuration that will be deployed
B. Status links to job list. Jobs will now print exact configuration files that will be used too:
C. Exact cmdline is repeated so you can restart if needed.