Need a layer performance test with viewport constrained layers. |
|||||
Issue descriptionIf a root layer has viewport constrained objects, this triggers a full compositing inputs update when scrolling. The rendering.mobile/google_web_search_mobile_2018 is such a page. We should add a case with high number of layers in "tough_compositing_cases" to monitor this.
,
Sep 4
,
Sep 28
,
Sep 28
I'm in the process of adding these tests here: http://crrev.com/c/1252634 The screenshot shows the difference in thread times on Nexus 4 with and without a fixed position element on top.
,
Sep 28
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/11ee84bf640000
,
Sep 29
📍 Job complete. See results below. https://pinpoint-dot-chromeperf.appspot.com/job/11ee84bf640000
,
Sep 29
,
Oct 3
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e4453a95e9b19f2c70818f229d3e1c4f00512fc8 commit e4453a95e9b19f2c70818f229d3e1c4f00512fc8 Author: Victor Miura <vmiura@chromium.org> Date: Wed Oct 03 04:00:55 2018 Add layer performance tests with viewport constrained layers. Adds stories for root scroller cases, with a "position:fixed" element on top. BUG= 880195 Change-Id: I3b293a1818225aca5807adc60f5db3954d61eb95 Reviewed-on: https://chromium-review.googlesource.com/c/1252634 Reviewed-by: Annie Sullivan <sullivan@chromium.org> Commit-Queue: Victor Miura <vmiura@chromium.org> Cr-Commit-Position: refs/heads/master@{#596117} [add] https://crrev.com/e4453a95e9b19f2c70818f229d3e1c4f00512fc8/chrome/test/data/perf/tough_compositor_cases/infinite_scroll_root_fixed_n_layers.html [modify] https://crrev.com/e4453a95e9b19f2c70818f229d3e1c4f00512fc8/tools/perf/page_sets/rendering/tough_compositor_cases.py
,
Oct 3
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by vmi...@chromium.org
, Sep 4