Issue metadata
Sign in to add a comment
|
7.4%-9.8% regression in loading.mobile at 530042:530104 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jan 22 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12bba898840000
,
Jan 22 2018
๐ Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12bba898840000
,
Jan 23 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ded4f8840000
,
Jan 23 2018
๐ Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14ded4f8840000
,
Jan 29 2018
+dtu, simonhatch: Any idea why these bisects didn't produce values? Trying on N7.
,
Jan 29 2018
๐ Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/149ac9da840000
,
Jan 29 2018
,
Jan 30 2018
๐ Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/149ac9da840000 Always use backpressure for fetch By ricea@chromium.org ยท Thu Jan 18 06:11:48 2018 chromium @ e0eac774de0cea10625eea2cb68f70310b05f764 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Jan 30 2018
I think I will have to revert it, at least for M65. Could you tell me where to find the "To Run This Test" link?
,
Jan 30 2018
,
Mar 22 2018
The change has been reverted. To avoid confusion, I am closing this issue. I have created a issue 824650 to track the work to re-land without a performance regression. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jan 22 2018