Issue metadata
Sign in to add a comment
|
3.9%-36.3% regression in rendering.mobile at 591349:592548 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 20
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/14581597640000
,
Sep 21
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/14581597640000 Telemetry: fix a SF stats collector bug by chiniforooshan@chromium.org https://chromium.googlesource.com/catapult/+/5f6da8a57db16291c01a894083137c294b3b4e5f 36.96 → No values Roll src/third_party/catapult 92ef0386b8b6..582a06eb7835 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/70b00be276bf695d4e4f72a075eb3d9454eaedd1 No values → 43.87 Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 20