Wouldn't (U)HD video on desktop be what it would improve, perf- and power-wise? [Memory bandwidth](https://mozillagfx.wordpress.com/2019/04/30/webrender-newsletter-44/) is WebRender's top problem: > While most recent discreet GPUs can stomach about anything we throw at them, integrated GPUs operate on a much tighter budget and compete with the CPU for memory bandwidth. 4k screens are real little memory bandwidth eating monsters. Windows seems to have it already. In bug 1479792 they want to do this for WebRender/Mac to improve YouTube (bug 1536515). Links added by me: > This is probably the path that gets taken for things like software-decoded video. We can improve this by having Gecko do the upload (which will be using ClientStorage from an existing code path) and then expose the texture to WebRender as an [external-image-native-texture](https://searchfox.org/mozilla-central/search?q=NativeTextureToWrExternalImage&path=) rather than as a [bag of bytes](https://searchfox.org/mozilla-central/search?q=RawDataToWrExternalImage&path=). I'll file a separate bug about this. (I thought we already had one on it but I cannot find it at the moment.)
Bug 1629788 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Wouldn't (U)HD video on desktop be what it would improve, perf- and power-wise? [Memory bandwidth](https://mozillagfx.wordpress.com/2019/04/30/webrender-newsletter-44/) is WebRender's top problem: > While most recent discreet GPUs can stomach about anything we throw at them, integrated GPUs operate on a much tighter budget and compete with the CPU for memory bandwidth. 4k screens are real little memory bandwidth eating monsters. Windows seems to have it already. In bug 1479792 it seems they want to do this for WebRender/Mac to improve YouTube (bug 1536515). Links added by me: > This is probably the path that gets taken for things like software-decoded video. We can improve this by having Gecko do the upload (which will be using ClientStorage from an existing code path) and then expose the texture to WebRender as an [external-image-native-texture](https://searchfox.org/mozilla-central/search?q=NativeTextureToWrExternalImage&path=) rather than as a [bag of bytes](https://searchfox.org/mozilla-central/search?q=RawDataToWrExternalImage&path=). I'll file a separate bug about this. (I thought we already had one on it but I cannot find it at the moment.)