c081515aa5
The website that's currently linked is deprecated so replacing with a link to the public Android Studio instructions (which are referenced from some other docs already). I've also removed the avocado suggestion, as from the bug it seems that a more scalable approach would be to have the build system do this rather than requiring each developer to set up tooling to achieve very small gains. Change-Id: Id20bdd8ee4c9da6701004c702579c16a1d819860 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3709947 Reviewed-by: Andrew Grieve <agrieve@chromium.org> Auto-Submit: James Lee <ljjlee@google.com> Commit-Queue: Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/main@{#1014920}
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.