Issue metadata
Sign in to add a comment
|
6% regression in system_health.memory_desktop at 542494:542578 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/13e9b369440000
,
Mar 20 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/134daeb9440000
,
Mar 21 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/13e9b369440000 Add fieldtrial testing config for new media controls by steimel@chromium.org https://chromium.googlesource.com/chromium/src/+/fdfc5ae4154a67e0539b9d0a77b3c5e2da38f40b Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Mar 21 2018
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/134daeb9440000 Add fieldtrial testing config for new media controls by steimel@chromium.org https://chromium.googlesource.com/chromium/src/+/fdfc5ae4154a67e0539b9d0a77b3c5e2da38f40b Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 2 2018
,
May 2 2018
,
May 9 2018
beccahughes, can you help triage this bug? Should the fieldtrial config be turned off? If not, does it block bug 833461?
,
May 9 2018
This was triggered when we enabled the new media controls field trial. The performance regression is for the entire new media controls feature. We have done lots of work since to improve the performance of the new controls and we think we are in reasonable place now. I am going to archive this bug for now. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 20 2018