Issue metadata
Sign in to add a comment
|
2.1%-8.2% regression in thread_raster_cpu_time_per_frame,thread_total_all_cpu_time_per_frame at 622113:622234 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 16
(6 days ago)
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/161371e0540000
,
Jan 16
(6 days ago)
😿 Pinpoint job stopped with an error. https://pinpoint-dot-chromeperf.appspot.com/job/161371e0540000 All of the runs failed. The most common error (20/20 runs) was: ReadValueError: Could not find values matching: {'story': u'infinite_scrolling', 'histogram': u'thread_total_all_cpu_time_per_frame'}
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14b9202c540000
,
Jan 16
(6 days ago)
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14b9202c540000 Enable ImplicitRootScroller by bokan@chromium.org https://chromium.googlesource.com/chromium/src/+/5173a50d9c7bac6890ee3070a49a437c43275e00 thread_total_all_cpu_time_per_frame: 24.05 → 26.13 (+2.086) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Jan 18
(4 days ago)
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 16 (6 days ago)