macOS power consumption fixes starting to land in Firefox, thanks to @markusstange:https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c33 …
-
-
Replying to @pcwalton @markusstange
ah this is fantastic, i was getting worried by the dissapointing-sounding results you were discussing last week!
1 reply 0 retweets 0 likes -
oh wait those number are non-wr aren’t they, rip
1 reply 0 retweets 0 likes -
Replying to @Gankra_ @markusstange
Is it not helping on WR? Or has it just not been implemented yet?
1 reply 0 retweets 0 likes -
Replying to @pcwalton @markusstange
Markus can speak to this better but basically webrender is much more gpu bandwidth hungry, and it’s drowning out the wins from these kinds of improvements
1 reply 0 retweets 0 likes -
Replying to @Gankra_ @markusstange
That’s odd, even with picture caching? I would have thought the bandwidth would basically be the same for small changes like that.
1 reply 0 retweets 0 likes -
Replying to @pcwalton @markusstange
does FrameLayerBuilder not composite its layers on the cpu? (never paid any attention to it)
1 reply 0 retweets 0 likes -
Replying to @Gankra_ @markusstange
It should be using OpenGL to composite cached textures. So it’s fundamentally doing the same thing WR with picture caching is.
1 reply 0 retweets 0 likes
That said, the OpenGL code in CompositorOGL is a lot simpler, basically just texture blits and not much else. Not even UBOs or anything like that. WR does a lot more, so there are more ways for it to go wrong. Not surprised WR is worse right now, though I suspect it’s fixable.
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.