Telemetry now supports sending a job directly to the performance try bots.
There are python scripts for automating the process of building, and testing commits against tip of tree and comparing performance. The performance try bots have been built on top of the bisect bot architecture. The bot works by syncing to the specified revision, applying your patch, building Chrome, and running the performance test. It then reverts your patch, builds again, and runs the performance test a second time. Results are output on the waterfall, as well as uploaded to cloud storage.
For information about using the performance try bots to perform a bisect, see Bisecting Performance Regressions.
The performance try server is tryserver.chromium.perf.
You can list the supported trybots by passing the --browser=list argument to tools/perf/run_benchmark. Here is the current output:
Starting a perf try job
From your src/ directory, run
Submitting jobs with blink patches
The same command works with blink patches. However, you cannot currently submit a tryjob with changes in BOTH the chromium and blink repositories--only the chromium changes will be tried.
Tips about test run time
You'll get an email when the results come in. In the buildbot output, you'll see a link to HTML results:
When you click the link, you'll get a page with results.
In the "Test" column, you can see all the metrics that were measured. When you click on one, you'll see the values for each run with the patch on the left ("Patch"), and without on the right ("ToT").