616b8605e6
This should make android-binary-size more clear about the size impact of commits. Previously all small native code changes would have a normalized size delta of 0 or 4kb. Bug: 921160 Change-Id: Ifa98681fc9f92d9e238140782153513927ae2f97 Reviewed-on: https://chromium-review.googlesource.com/c/1423663 Commit-Queue: agrieve <agrieve@chromium.org> Auto-Submit: agrieve <agrieve@chromium.org> Reviewed-by: Eric Stevenson <estevenson@chromium.org> Cr-Commit-Position: refs/heads/master@{#624669}
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 tracks: Most of the speed work on Chrome is organized into these tracks.
- 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.
For Googlers
- We have a bi-weekly meeting to keep everyone in sync. Join chrome-speed@ or contact benhenry@chromium.org for more information.
- Have something to include in our Milestone-based Speed report to the Chrome team? Please keep track of it here.