Issue metadata
Sign in to add a comment
|
31.4% regression in loading.mobile at 605202:605206 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16bfe399e40000
,
Nov 8
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/16bfe399e40000
,
Nov 9
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/12b6c6cfe40000
,
Nov 10
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/12b6c6cfe40000 Clean up the Java method name for recording a sparse histogram by isherman@chromium.org https://chromium.googlesource.com/chromium/src/+/9dae03c6b8e1255ef565d738296e73cf4325a6ff timeToFirstContentfulPaint: 6.68e+04 → No values Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/loading-benchmarks
,
Nov 13
The bisect landed on a renaming change, which seems tremendously unlikely to have had any meaningful performance impact.
,
Nov 13
The graph is fairly noisy, might have been a bad bisect, lets try again.
,
Nov 13
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/170f034be40000
,
Nov 13
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/170f034be40000 Clean up the Java method name for recording a sparse histogram by isherman@chromium.org https://chromium.googlesource.com/chromium/src/+/9dae03c6b8e1255ef565d738296e73cf4325a6ff timeToFirstContentfulPaint: 6.673e+04 → No values Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/loading-benchmarks
,
Jan 11
Assigned, but no owner or component? Please find a component and/or owner |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8