Re:RenderingNG: Ready for the next generation of web content
by floatboth on Friday July 02, 2021 @08:21AM
(#27710508)
> one needs to tinker with even more flags to get Firefox to acceptable performance
All you need is gfx.webrender.all, if you even failed the qualification (most modern setups shouldn't fail it).
Re:RenderingNG: Ready for the next generation of web content
by bufferoverflow on Friday July 02, 2021 @06:15AM
(#27709765)
Seriously, FF on Ubuntu causes 100% CPU usage when watching YouTube in 1080p. Meanwhile Chrome on Windows eats maybe 6-10%.
How is this not #1 priority to fix?
Re:RenderingNG: Ready for the next generation of web content
by magicalhippo on Friday July 02, 2021 @07:43AM
(#27710224)
Not much FF can do directly AFAIK, since it has to do with the hardware decoding the drivers support.
I've used an addon for a while which fixed it by forcing YouTube to serve h264 rather than vp9 content, as hardware accelerated decoding of h264 worked but not vp9. But lately it hasn't worked well. Haven't investigated if it was due to newer content only being vp9 or if the addon stopped working.
Re:RenderingNG: Ready for the next generation of web content
by GrayShade on Friday July 02, 2021 @08:43AM
(#27710745)
I think it's a conflict with the sandbox, like it https://bugzilla.mozilla.org/show_bug.cgi?id=1698778.
Re:RenderingNG: Ready for the next generation of web content
by muizelaar on Friday July 02, 2021 @09:06AM
(#27710992)
I'm pretty sure most users don't have this experience. Can you post a link to a pastebin of your about:support or file a bug?
Re:RenderingNG: Ready for the next generation of web content
by TingPing on Friday July 02, 2021 @11:06AM
(#27712470)
This is normal. Firefox is only now rolling out accelerated decoding on Linux.
Re:RenderingNG: Ready for the next generation of web content
by roca on Friday July 02, 2021 @06:57AM
(#27709970)
Comparing across platforms is not a good idea. Different drivers, APIs and platform OS issues dramatically affect these results.
Re:RenderingNG: Ready for the next generation of web content
by roca on Friday July 02, 2021 @07:19AM
(#27710090)
Personally I just have layers.acceleration.force-enabled: true and that's enough to get me fast 4K WebGL. WebRender and Wayland dmabuf seem to turn on automatically. Intel 915, Fedora 34, dual 4K monitors, distro Firefox 89.
Re:RenderingNG: Ready for the next generation of web content
by GrayShade on Friday July 02, 2021 @08:44AM
(#27710756)
Note that WebRender obsoletes Layers, so you shouldn't need to set that.
Re:RenderingNG: Ready for the next generation of web content
by AHTERIX5000 on Friday July 02, 2021 @06:52AM
(#27709950)
Yeah it's not great on Mac either. I have pretty much standard Firefox installation with only Ublock Origin added and it's extremely easy to get 16" Macbook Pro hot when Safari handles the same load without too much heat.
Out of the box, Firefox has terrible rendering performance, not to mention hw-accelerated video decoding. Now, Chrome is not a whole lot better out of the box, since it still applies old "Driver bug workarounds" that have long been fixed in mesa/GPU drivers, but this is easy to circumvent with the `--disable-gpu-driver-bug-workarounds`.
I've been running Chromium with the said flag for over half a decade now, and I have yet to see one of the bugs manifest. Firefox on the other hand, has a similar entry in `about:config`, but one needs to tinker with even more flags to get Firefox to acceptable performance (Somehow, enabling xrender makes WebGL fast, but makes video decoding have weird jitter, etc).
The day Firefox gets comparable WebGL/video decode performance will most likely be the day I switch.