Issue metadata
Sign in to add a comment
|
31.4% regression in loading.desktop at 552597:552602 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 25 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14fe8b09c40000
,
Apr 25 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/14fe8b09c40000
,
May 8 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14ed5c2fc40000
,
May 10 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14ed5c2fc40000 Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd [infra] Use builder_view_only for try builder groups (consoles). by tandrii@chromium.org https://chromium.googlesource.com/chromium/src/+/fd46b735fa9fe3aab004f4f08dd39393b5f24474 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
May 10 2018
The metric that is shown as regressesing (in https://chromeperf.appspot.com/group_report?bug_id=836533 and https://pinpoint-dot-chromeperf.appspot.com/job/14ed5c2fc40000) is timeToFirstMeaningfulPaint. Therefore, I think we should dupe this bug against issue 836469 and continue the investigation overthere.
,
May 10 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Apr 25 2018