Issue metadata
Sign in to add a comment
|
A zero-to-nonzero to 5% regression in rendering.mobile at 587358:587450 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 4
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11be49ab640000
,
Sep 5
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11be49ab640000
,
Sep 18
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12f40a0f640000
,
Sep 18
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12f40a0f640000 turn off use-zoom-for-dsf on Android by eirage@chromium.org https://chromium.googlesource.com/chromium/src/+/14d5c4330c08ac9bcdcda7960561e3e92c135da6 258.9 → 271.9 (+13.01) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Sep 18
regression at commit #587380 is caused by turning off zoom-for-dsf which is turning on at commit #579542. There is a similar improvement when enable (around July 31). |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 4