7 ms·
With a compositor you're already drawing every pixel every frame on the GPU, whether it's just a cursor blinking or not. The WR approach basically only adds a n
by pcwalton 9y ago
With a compositor you're already drawing every pixel every frame on the GPU, whether it's just a cursor blinking or not. The WR approach basically only adds a negligible amount of vertex shading time.
- drudru11 9y agoBut only on a change... So if the cursor blinks every second, you would be doing the render/composite at that point.
- Rusky 9y agoWebRender does exactly the same thing.
- randyrand 9y agoIt seems like even in the compositor approach, you could optimize that. copy the last last drawn frame buffer directly and then modify it. I think the best approach would be some hybrid between invalidation and redrawing everything.
- lightedman 9y agoIIRC GPUs already do a more efficient version of what you're proposing, at least the mobile ones, by using tile-based rendering. Thus only the general area of the screen that changes gets modified while the remainder is static. This way you can easily control how many GPU cores are actively changing and thus need power, while you keep the static state in the other cores and they consume negligible power.