Issue metadata
Sign in to add a comment
|
2.6%-29.6% regression in rendering.mobile at 589781:589786 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 13
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/178d2553640000
,
Sep 13
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/178d2553640000
,
Sep 14
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/17ed6179640000
,
Sep 14
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/17ed6179640000 Canvas/WebGL: Defer commits to limit queued frames. by ericrk@chromium.org https://chromium.googlesource.com/chromium/src/+/0dd63a3394566a94619974f91ce14f8d7680512c 46.52 → 48.67 (+2.15) Change the type of QuicFrames from std::vector to QuicInlinedVector. Not protected. by wub@chromium.org https://chromium.googlesource.com/chromium/src/+/13fcb7a385bb562c1c5912f977dd149b8bba65b5 48.54 → 49.33 (+0.7908) Understanding performance regressions: http://g.co/ChromePerformanceRegressions Benchmark documentation link: https://bit.ly/rendering-benchmarks
,
Oct 30
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 13