Confirmed users
44
edits
Gecko:OffMainThreadPainting: Difference between revisions
→Proposed solution
Mattwoodrow (talk | contribs) No edit summary |
Mattwoodrow (talk | contribs) |
||
| Line 14: | Line 14: | ||
Modify our current display item list items to be entirely self contained, such that they only access main-thread data during construction (or an explicit finalization pass). We can then pass the entire tree across to the painting thread to do all visibility analysis, layer building and ThebesLayer painting. This would require that ownership and access to FrameLayerBuilder and Layers become painting-thread only, instead of main-thread only as they currently. Compositing then happens on yet another thread via off-main-thread compositing (OMTC - Bug 598873). | Modify our current display item list items to be entirely self contained, such that they only access main-thread data during construction (or an explicit finalization pass). We can then pass the entire tree across to the painting thread to do all visibility analysis, layer building and ThebesLayer painting. This would require that ownership and access to FrameLayerBuilder and Layers become painting-thread only, instead of main-thread only as they currently. Compositing then happens on yet another thread via off-main-thread compositing (OMTC - Bug 598873). | ||
The painting thread could use worker threads for the actual rasterization pass, so that we can have multiple paints being done in parallel. | |||
We can also start retaining the display item list on the painting thread. This, once it is integrated with async scrolling (AZPC) would let us rasterize new content during content without accessing the main-thread. We could build a layer tree for the entire page, but only rasterize content that falls within the prerendered viewport. When async scrolling attempts to scroll outside of the prerendered area, we would notify the painting thread of the new desired prerendered area and rasterize it. | We can also start retaining the display item list on the painting thread. This, once it is integrated with async scrolling (AZPC) would let us rasterize new content during content without accessing the main-thread. We could build a layer tree for the entire page, but only rasterize content that falls within the prerendered viewport. When async scrolling attempts to scroll outside of the prerendered area, we would notify the painting thread of the new desired prerendered area and rasterize it. | ||