Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 2.6% regression in rendering.mobile/thread_total_all_cpu_time_per_frame at 612639:612810 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 3
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/10c93572140000
,
Dec 3
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/10c93572140000 HTTP status code 401: Login Required
,
Dec 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/116f8c1fe40000
,
Dec 4
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/116f8c1fe40000 Removing the kInlineTransform compositing reason by masonfreed@chromium.org https://chromium.googlesource.com/chromium/src/+/f6e075c54c8bc6130d49c09ad3df6944376ccba4 thread_total_all_cpu_time_per_frame: 11.26 → 13.42 (+2.159) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Dec 18
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 3