cee6f35d93
- Split "realtime" into the two different concepts we've been conflating. "Immediate" means we know immediately when the metric occurred. "Performant to compute" means we can compute it in a RUM context. - Fill in/update the TTI example. Change-Id: I5bf1ea0357eb4b7c3f81b3a0e4112d48ec3f2296 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2230930 Commit-Queue: Annie Sullivan <sullivan@chromium.org> Reviewed-by: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#775301}
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.