5e847c6565
Add instructions on how to use the compile-size builder and fix issues. This is necessary before we block CLs in CQ that have large increases. Bug: 370594503 Change-Id: I035ea17a6687457dac0060ce28f843319a564687 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6246737 Commit-Queue: Erik Staab <estaab@chromium.org> Reviewed-by: Junji Watanabe <jwata@google.com> Reviewed-by: Hans Wennborg <hans@chromium.org> Cr-Commit-Position: refs/heads/main@{#1418813}
Chrome Speed
Contact information
- Contact: speed@chromium.org
- Escalation:
- benhenry@chromium.org (TPM)
- File a bug: template
- Regression postmortem: template
User Docs
- How does Chrome measure performance?
- My CL caused a performance regression! What do I do?
- I want Chrome to have better performance
- I want to add tests or platforms to the perf waterfall
Core Teams and Work
- Speed domain area experts: These mailing lists and bug triage rotations provide expertise into specific domain areas of Speed: memory, power, loading, responsiveness, binary size, data usage, and browser UI.
- Chrome Speed Operations: provides the
benchmarks, infrastructure, and releasing oversight to track regressions.
- Benchmark-specific discussion: benchmarking-dev@chromium.org
- Performance dashboard, bisect, try jobs: speed-services-dev@chromium.org
- Chrome Speed Metrics: provides a set of high-quality metrics that represent real-world user experience, and exposes these metrics to both Chrome and Web Developers.
- General discussion: speed-metrics-dev@chromium.org
- The actual metrics: speed launch metrics survey.