Issue metadata
Sign in to add a comment
|
74.3% regression in loading.mobile at 533259:533274 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 2 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16c316de840000
,
Feb 3 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16c316de840000
,
Feb 5 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12853f61840000
,
Feb 5 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/12853f61840000
,
Mar 3 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14832fdc440000
,
Mar 3 2018
Trying a bisect on a wider range.
,
Mar 4 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/14832fdc440000 Enable SpeculativePreconnect Field Trial Testing by alexilin@chromium.org https://chromium.googlesource.com/chromium/src/+/8442e044284223377ccd75e4f1b519c5656d4d8d Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Apr 24 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14f42d79c40000
,
Apr 24 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14f42d79c40000
,
Oct 22
This feature added a lot of noise after enabling to one particular story (FlipKart_hot_3g). The android-nexus5 bot was replaced with the "Android Nexus5 Perf" bot since then and now this new bot shows little amount of noise. I consider this issue is obsolete and not actionable. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 2 2018