| OLD | NEW |
| (Empty) | |
| 1 # chromium.perf Waterfall |
| 2 |
| 3 ## Overview |
| 4 |
| 5 The [chromium.perf waterfall](http://build.chromium.org/p/chromium.perf/waterfal
l) |
| 6 continuously builds and runs our performance tests on real Android, Windows, |
| 7 Mac, and Linux hardware. Results are reported to the |
| 8 [Performance Dashboard](https://chromeperf.appspot.com/) for analysis. The |
| 9 [Perfbot Health Sheriffing Rotation](perf_bot_sheriffing.md) keeps the build |
| 10 green and files bugs on regressions. They maintain |
| 11 [Chrome's Core Principles](https://www.chromium.org/developers/core-principles) |
| 12 of speed: |
| 13 |
| 14 > "If you make a change that regresses measured performance, you will be |
| 15 > required to fix it or revert". |
| 16 |
| 17 ## Contact |
| 18 |
| 19 * You can reach the Chromium performance sheriffs at perf-sheriffs@chromium.or
g. |
| 20 * Bugs on waterfall issues should have Component: |
| 21 [Speed>Benchmarks>Waterfall](https://bugs.chromium.org/p/chromium/issues/lis
t?can=2&q=component%3ASpeed%3EBenchmarks%3EWaterfall+&colspec=ID+Pri+M+Stars+Rel
easeBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=id
s). |
| 22 |
| 23 ## Links |
| 24 |
| 25 * [Perfbot Health Sheriffing Rotation](perf_bot_sheriffing.md) |
| 26 * [Debugging an Android Perf Failure](perf_bot_sheriffing.md#Android-Device-fa
ilures) |
| 27 * TODO: Page on how to repro failures locally |
| 28 * TODO: Page on how to connect to bot in lab |
| 29 * TODO: Page on how to hack on buildbot/recipe code |
| 30 * TODO: Page on bringing up new hardware |
| OLD | NEW |