Issue metadata
Sign in to add a comment
|
14.2% regression in media.mobile at 585830:586693 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 30
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12a3dde1640000
,
Aug 31
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12c86525640000
,
Sep 3
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12a3dde1640000 gpu: disable oop raster on Adreno Lollipop and earlier by enne@chromium.org https://chromium.googlesource.com/chromium/src/+/4b51d24604846cd3d049946e70e9ccb535a4b0c2 8.105e+06 → 8.616e+06 (+5.112e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Sep 4
,
Sep 4
nednguyen: is there a reason the perf bots are still running Lollipop? I guess I'm surprised that this is the case. At any rate, this bug is me disabling a new feature for correctness reasons. This is WontFix in general.
,
Sep 4
,
Sep 4
We are actually gonna remove this configuration once we have Pixel 2 configuration available (see http://go/perf-devices-2018)
,
Sep 6
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12c86525640000 gpu: disable oop raster on Adreno Lollipop and earlier by enne@chromium.org https://chromium.googlesource.com/chromium/src/+/4b51d24604846cd3d049946e70e9ccb535a4b0c2 8.046e+06 → 8.616e+06 (+5.702e+05) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: None |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 30