Pipe dream: A WebRender front end that processes display lists on GPU via compute shader and multi-draw indirect. i.e. just hand CSS off to the hardware. CSS isn’t going anywhere. We might as well teach our graphics hardware to speak it natively.
-
-
Replying to @pcwalton
There is a lot of stuff in WR that is inherently more efficient to do on the CPU, but handing off things like culling to compute shaders would be neat
1 reply 0 retweets 0 likes -
Replying to @nicalsilva
Yeah. Even if some things are slower on GPU it might be nice to just free up the CPU for other work though.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
On low-end-ish hardware (which is a large part of the population) we don't have that much leeway to fill high resolution screens on the GPU for pages with significant overdrawn, so I would rather stick to only have it do the things it shines at
1 reply 0 retweets 0 likes -
Replying to @nicalsilva @pcwalton
That said if we tried hard we'd probably find that there's more of it that the GPU could do efficiently than I imply. In any case designing a rendering system from scratch (free of css specifics) and molding it around the strengths and weaknesses of compute would be interesting
1 reply 0 retweets 1 like
It might be possible to tweak the display list format so that more of it can be handed off directly to the GPU. Mesh shaders are potentially interesting here.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.