b9941a6100
Extend the lifetime of Startup.Android.Cold.TimeToFirstContentfulPaint3. The histogram as it is mentioned in the histograms.xml has no data on the UMA dashboard because the collected histogram adds the suffix ".Tabbed". Register this suffix in the histogram_suffixes_list to make it searchable in the dashboard. Mark the histogram without the suffix as base="true" to make it non-searchable (to avoid confusions). Adjust the doc and the test accordingly. Bug: 40926074, 384509264 Change-Id: Id7653a49fd8fff67df5fd046011b2d233d93b779 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6110414 Owners-Override: Nafis Abedin <nafisabedin@google.com> Reviewed-by: Andrew Grieve <agrieve@chromium.org> Commit-Queue: Egor Pasko <pasko@chromium.org> Cr-Commit-Position: refs/heads/main@{#1398663}
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.