Issue metadata
Sign in to add a comment
|
18.4% regression in system_health.memory_mobile at 541744:541759 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 14 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14cfe57e440000
,
Mar 14 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14cfe57e440000 Roll AFDO from 67.0.3364.0_rc-r1 to 67.0.3365.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/c2b84ad191135be504a0abf4860b97b59f9d8b52 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 16 2018
+gbiv fyi the roll seems to cause a small runtime memory regression on one benchmark. Only one website on one device though so closing as won't fix.
,
Mar 16 2018
Issue 821400 has been merged into this issue.
,
Mar 16 2018
Issue 821401 has been merged into this issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 14 2018