Issue metadata
Sign in to add a comment
|
21.1%-49.9% regression in v8.browsing_mobile at 588394:588429 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 18
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13837483640000
,
Sep 18
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/13837483640000 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 355 → 493.2 (+138.2) 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 Benchmark documentation link: None
,
Sep 18
This is expected due to: 2018-09-03 pasko@chromium.org devil: Limit CPU/GPU frequency for Nexus 5X 2 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 18