The vast majority of pages do just fine with WebRender when repainting every frame. There are a bunch that don’t, but there are also a bunch that perform badly with the traditional stack.
-
-
Replying to @pcwalton
The percentages don't really matter; if important/major pages run fine in vanilla gecko but not webrender, but a bunch of oddball pages run great in webrender, I don't think that's a win (and I don't think we could politically sell shipping that either)
2 replies 0 retweets 0 likes -
Replying to @Gankra_
I actually pretty much entirely disagree with your take—the biggest problem is that we don’t control the OS compositor, so we need invalidation and so forth in order to get good energy efficiency. We’ve already proven that you can get good FPS in the repaint-everything case.
1 reply 0 retweets 0 likes -
Replying to @pcwalton
I am certain we haven't? Tons of cases where a page just slaps 5+ text-shadows on something and we fall over completely. *even* if we cache the blurs, just compositing them is too expensive. glenn is heads down working on picture caching because we have so many of these bugs!
1 reply 0 retweets 0 likes -
Replying to @Gankra_
I knew you were going to bring up that case :) That is easy to fix: just cache the blurs together. Much easier than picture caching. The reason why we need picture caching, in my view, is energy efficiency, not to get 60 FPS.
2 replies 0 retweets 0 likes -
-
Replying to @Gankra_
Picture caching is a lot more than just text shadows. That’s why it’s been so much work to implement.
2 replies 0 retweets 0 likes -
Replying to @pcwalton
ok sure, but it's just "the right" solution to the text-shadow issue, in the same way that MIR was "the right" solution to borrowck, even though it wasn't a technical requirement :)
1 reply 0 retweets 0 likes -
also energy efficiency is technically a requirement to hit 60fps -- my macbook pro can't even play fullscreen videos at 60fps when it starts thermal throttling :(
1 reply 0 retweets 0 likes -
Replying to @Gankra_
A lot of it is that we are at the mercy of what the OS compositor (in this case, Core Animation) supports. You basically have to tile traditionally or eat one or more full window blits every frame.
1 reply 0 retweets 2 likes
I feel like if I have to eat crow, not considering the hidden tax of the OS compositor is the biggest issue. Fortunately it’s fixable. Also note that Gecko is terrible at using the OS compositor right now and WR will be an improvement there.
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.