4b18d0c047
Approved on https://groups.google.com/a/chromium.org/g/cxx/c/lVQOJTng1RU. Bug: none Change-Id: Ibe0f8f16bce55b3ede4c1e1d2720e83e8dd4faf0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5852373 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Owners-Override: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/main@{#1356840}
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
- Perf sheriffing documentation
- 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.