Issue metadata
Sign in to add a comment
|
24.2%-50.4% regression in rasterize_and_record_micro.top_25 at 588394:588429 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1336e1e5640000
,
Sep 5
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/1336e1e5640000 Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/fcfe9a6f17f02771890c03d666dcebf560eca909 0.1366 → 0.1998 (+0.0632) Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult 713e916190aa..88dc49aaadb0 (3 commits)" is a roll. Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Sep 5
Almost certainly due to: 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X Which is working as intended. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 4