Issue metadata
Sign in to add a comment
|
5.4%-109.7% regression in system_health.common_desktop at 552292:554551 |
||||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 1 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/149dc8adc40000
,
May 1 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/149dc8adc40000 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 1 2018
My commit crrev/fd46b735fa9fe3aab004f4f08dd39393b5f24474 doesn't take part in build, let alone build artifacts. Either benchmark is too noisy (percentages in title don't inspire confidence) or this is another commit in the list above. lukasza@chromium.org wdyt?
,
May 1 2018
The pinpoint job in #c3 points out a regression in timeToFirstPaint. Therefore, I think it is fair to resolve this bug as a duplicate of issue 836469 where we track a regression in timeToFirstContentfulPaint. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 1 2018