Issue metadata
Sign in to add a comment
|
2.7%-95.2% regression in rendering.mobile/frame_times at 591349:594038 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 1
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/113a5bb7640000
,
Oct 2
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/113a5bb7640000 Use vpython and remove vendored pymock. by jbudorick@chromium.org https://chromium.googlesource.com/catapult/+/23c67a511280f6dbc2a2bea849dd7eed5104809e 0.6189 → No values Roll src/third_party/catapult e06567b30fdd..64f2ed4bb2f1 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com https://chromium.googlesource.com/chromium/src/+/276e662dbc2525240c0d3abe456086f11d04843b No values → 1.206 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
, Oct 1