Issue metadata
Sign in to add a comment
|
5.4%-36.1% regression in media.mobile at 597295:597387 |
||||||||||||||||||||||||
Issue descriptionThese 16 alerts look valid, though more recently their traces have *more* than recovered (better than before these alerts). Doing a bisect to help inform regression culprit owner of this (though the regression itself might already have been fixed).
,
Oct 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12c90728e40000
,
Oct 10
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12c90728e40000 Revert "solid color quads workaround for use-zoom-for-dsf" by eirage@chromium.org https://chromium.googlesource.com/chromium/src/+/d7d5990bc6b25d7b7ce711b035147030e778879a cpu_time_percentage: 0.434 → 0.5846 (+0.1506) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None
,
Oct 10
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 9