Issue metadata
Sign in to add a comment
|
6% regression in rasterize_and_record_micro.top_25 at 516344:516486 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 24 2017
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16fccb87f80000
,
Nov 26 2017
๐ Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/16fccb87f80000 Revert "Update static snapshot for a batch of Google sites." By wkorman@chromium.org ยท Tue Nov 14 21:36:50 2017 chromium @ 0d1b568fe9d6e44bb2829841f7e6b0b533cfccba Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Dec 7 2017
Ping wkorman, could you take a look?
,
Dec 8 2017
Transferring these to vmpstr@ as owner of the involved benchmark. Note that the r_and_r benchmark is in consideration to be replaced (for perf regression monitoring purposes at least) by an updated repaint benchmark. More on that at issue 770800.
,
Jan 22 2018
vmpstr: any update on this bug?
,
Feb 5 2018
,
Mar 26 2018
According to pinpoint this is a change as a result of updating pagesets. If that's the case this should be considered the new "norm" for the tests. Please re-open if you disagree. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 24 2017