Issue metadata
Sign in to add a comment
|
7.5%-52.8% regression in loading.mobile at 597570:597663 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 10
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/15d56312e40000
,
Oct 10
,
Oct 11
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11289c82e40000
,
Oct 11
On second look at the graphs, this looks like noise.
,
Oct 11
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/11289c82e40000
,
Oct 14
📍 Found a significant difference after 1 commit. https://pinpoint-dot-chromeperf.appspot.com/job/15d56312e40000 Roll src/third_party/catapult 4fc4281d2152..9ec8468cfde0 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/f80143088ca19a0af1fb3dd75e8503031ebaed25 timeToFirstContentfulPaint: 498.4 → 699 (+200.5) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/loading-benchmarks |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 10