4 ms·
I like the writeup and drawings, but I have to mention that this is a bit too specific to browsers as they work right now, specifically Chrome. Having to pay at
by pcwalton 8y ago
I like the writeup and drawings, but I have to mention that this is a bit too specific to browsers as they work right now, specifically Chrome. Having to pay attention to the paint/compositor distinction and layer count is something that newer renderers like WebRender make obsolete. You don't have to worry about layer count causing needless overdraw if you have a unified system so that occluded content is culled, for example.
WebRender is already turned on by default for many users in Firefox Nightly…
- lwansbrough 8y agoUnfortunately for Firefox this concept doesn’t work very well on the CPU it seems. Every time I open Firefox on my (slightly older but still very capable) MBP the fans go nuts and the CPU could fry an egg. Probably has something to do with my integrated graphics chip. And yeah I’m going to keep posting this anecdote until Mozilla acknowledges the problem.
- minitech 8y ago> WebRender is already turned on by default for many users in Firefox Nightly… Are you using Nightly?
- mccr8 8y agoDo you have scaled resolution enabled? If so, that sounds like this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 https://bugzilla.mozilla.org/show_bug.cgi?id=1404042 I think there's been a little bit of progress on that issue, but not much, unfortunately.
- pcwalton 8y agoSounds like Core Animation could fix that issue? I have a patch for that almost ready to go (mstange is testing it as we speak).