The web at maximum FPS: How WebRender gets rid of jank

Re:The web at maximum FPS: How WebRender gets rid of jank by Dylan16807 on Wednesday October 11, 2017 @03:56PM (#15452882)

In this use case the "painting" a compositor does from layers is copying one big rectangle. That takes next to zero time. That's not at all similar to "painting" where you actually re-render the entire visible portion of the page.

[ Parent | on HN ]

Re:The web at maximum FPS: How WebRender gets rid of jank by pcwalton on Wednesday October 11, 2017 @04:07PM (#15452987)

> That's not at all similar to "painting" where you actually re-render the entire visible portion of the page.

Why not?

Painting a page is mostly just copying pixels from textures too.

[ Parent | on HN ]

Re:The web at maximum FPS: How WebRender gets rid of jank by Dylan16807 on Wednesday October 11, 2017 @06:34PM (#15454140)

You don't see a notable difference between [tens of] thousands of glyphs and bits being layered on top of each other and processed through a display list, versus copying over one single rectangle from A to B?

[ Parent | on HN ]

Re:The web at maximum FPS: How WebRender gets rid of jank by pcwalton on Wednesday October 11, 2017 @06:48PM (#15454230)

No, I don't. It adds a small amount of vertex shading time. The GPU primitive rasterization machinery is extremely good.

Benchmark it yourself if you don't believe me!

[ Parent | on HN ]