Issue metadata
Sign in to add a comment
|
19% regression in blink_perf.layout at 558153:558156 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 18 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1296f0e4240000
,
May 19 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1296f0e4240000 Roll AFDO from 68.0.3428.0_rc-r1 to 68.0.3429.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/fcb575c8904446db7b5a84c93bf45cf06c5b50a8 Assigning to sheriff gbiv@chromium.org because "Roll AFDO from 68.0.3428.0_rc-r1 to 68.0.3429.0_rc-r1" is a roll. Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 22 2018
Ack; thanks. Will look into this along with issue 844584, since I'm seeing a similar (though less common) "AFDO roll happened, so the perf gets to change drastically, too" thing here. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 18 2018