Overall webrender is visibly jankier than non webrender while scrolling. as long as we don't render and only composite, scrolling is smooth, and if we render a handful of tile, scrolling is janky. Unfortunately, webrender tends to invalidate more than the layers backend for a lot of pages. For example google.com search result pages (search term "test"), have picture cache tiles invalidated constantly during scolling, while it looks like layers manage to invalidate very little.
Bug 1650724 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Overall webrender is visibly jankier than non webrender while scrolling. as long as we don't render and only composite, scrolling is smooth, and if we render a handful of tile, scrolling is janky. Unfortunately, webrender tends to invalidate more than the layers backend for a lot of pages. For example google.com search result pages (search term "test"), have picture cache tiles invalidated constantly during scolling, while it looks like layers manage to invalidate very little. On the CPU side, the renderer thread is often the bottleneck, with a lot of time spent submitting draw calls (some of which looks like it is sunk into ANGLE's state management code).