3519fdc637
We are switching to v4 metrics for startup. Adjust the description of the metric in histograms.xml to match the fact that it is the primary one. Rewrite the descriptions of the previous versions to focus only on the differences. This will allow readers to avoid doing the diff themselves. Bug: 384084655 Change-Id: Ief23b69bb15586737186a450c58bb0eceee2f2a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6197642 Reviewed-by: Sean Maher <spvw@chromium.org> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1414348}
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.