A benchmark owner is the main point of contact for a given benchmark. The owner is responsible for:
There can be multiple owners of a benchmark, for example if there are multiple types of metrics, or if one owner drives metric development and another drives performance improvements in an area.
src/tools/perf/benchmarks/benchmark_name.py
, where benchmark_name
is the part of the benchmark before the “.”, like smoothness
in smoothness.top_25_smooth
.Name
method that should match the full name of the benchmark.benchmark.Info
decorator above the class.Example:
@benchmark.Info( emails=['owner1@chromium.org', 'owner2@samsung.com'], component=’GoatTeleporter>Performance’, documentation_url='http://link.to/your_benchmark_documentation')
In this example, there are two owners for the benchmark, specified by email; a bug component, which will be automatically added to the bug by the perf dashboard; and a link to documentation (which will be added to regression bugs in Q3 2018).
tools/perf/generate_perf_data
to update tools/perf/benchmark.csv
.benchmark.csv
to a CL for review. Please add any previous owners to the review.src/tools/perf/core/perf_data_generator.py
.NON_TELEMETRY_BENCHMARKS
or NON_WATERFALL_BENCHMARKS
.BenchmarkMetadata
).tools/perf/generate_perf_data
to update tools/perf/benchmark.csv
.perf_data_generator.py
and benchmark.csv
to a CL for review. Please add any previous owners to the review.