Bug 1633273 Comment 3 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I just noticed that bug 1629140 caused a horrible performance regression (2 fps) for WebRender with native Wayland backend on KDE. Gnome is unaffected. Disabling widget.wayland_vsync.enabled fixes it. I will file a new bug about it.

There is a [whitelist](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxDriverInfo.cpp#456) that controls WebRender rollout: WebRender is enabled by default for [qualified](https://wiki.mozilla.org/Platform/GFX/WebRender_Where) systems as long as gfx.webrender.force-disabled hasn't been set to true. On Linux, it is enabled by default for [Nightly with Mesa drivers](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoX11.cpp#513), but for Intel only with [max. 4953600 pixels](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoBase.cpp#813).
It can be force-enabled with gfx.webrender.all (don't forget to restart Nightly). It is enabled if "Compositing" on about:support says "WebRender".
If your GPU ("Device ID" on about:support) is not on the whitelist, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender).
If WebRender is not enabled by default for your screen size, but performs well for you, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) to request enabling it by default for large screens on Intel/Linux.
Revision 1 by
on 
I just noticed that bug 1629140 caused a horrible performance regression (2 fps) for WebRender with native Wayland backend on KDE. Gnome is unaffected. Disabling widget.wayland_vsync.enabled fixes it. I will file a new bug about it.

There is a [whitelist](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxDriverInfo.cpp#456) that controls WebRender rollout: WebRender is enabled by default for [qualified](https://wiki.mozilla.org/Platform/GFX/WebRender_Where) systems as long as gfx.webrender.force-disabled hasn't been set to true. On Linux, it is enabled by default for [Nightly with Mesa drivers](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoX11.cpp#513), but for Intel only with [max. 4953600 pixels](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoBase.cpp#813).
It can be force-enabled with gfx.webrender.all (don't forget to restart Nightly). It is enabled if "Compositing" on about:support says "WebRender".
If your GPU ("Device ID" on about:support) is not on the whitelist, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender).
If WebRender is not enabled by default for your screen size, but performs well for you, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) to request enabling it by default for large screens on Intel/Linux. (If it performs bad, you could file a bug as well. :D bug 1620076 - and even later bug 1617498 - will help in the future.)
Revision 2 by
on 
I just noticed that bug 1629140 caused a horrible performance regression (2 fps) for WebRender with native Wayland backend on KDE. Gnome is unaffected. Disabling widget.wayland_vsync.enabled fixes it. I will file a new bug about it.

There is a [whitelist](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxDriverInfo.cpp#456) that controls WebRender rollout: WebRender is enabled by default for [qualified](https://wiki.mozilla.org/Platform/GFX/WebRender_Where) systems as long as gfx.webrender.force-disabled hasn't been set to true. On Linux, it is enabled by default for [Nightly with Mesa drivers](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoX11.cpp#513), but for Intel only with [max. 4953600 pixels](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoBase.cpp#813).
It can be force-enabled with gfx.webrender.all (don't forget to restart Nightly). It is enabled if "Compositing" on about:support says "WebRender".
If your GPU ("Device ID" on about:support) is not on the whitelist, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender).
If WebRender is not enabled by default for your screen size, but performs well for you, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) to request enabling it by default for large screens on Intel/Linux. (If it performs bad, you could file a bug as well. :D bug 1620076 and bug 1617498 will help in the future.)
Revision 3 by
on 
I just noticed that bug 1629140 caused a horrible performance regression (2 fps) for WebRender with native Wayland backend on KDE. Gnome is unaffected. Disabling widget.wayland_vsync.enabled fixes it. I will file a new bug about it.

There is a [whitelist](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxDriverInfo.cpp#456) that controls WebRender rollout: WebRender is enabled by default for [qualified](https://wiki.mozilla.org/Platform/GFX/WebRender_Where) systems as long as gfx.webrender.force-disabled hasn't been set to true. On Linux, it is enabled by default for [Nightly with Mesa drivers](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoX11.cpp#513), but for Intel only with [max. 4953600 pixels](https://searchfox.org/mozilla-central/rev/55a4faa52f72918efa51150d127aebdc057dc6cf/widget/GfxInfoBase.cpp#813).
It can be force-enabled with gfx.webrender.all (don't forget to restart Nightly). It is enabled if "Compositing" on about:support says "WebRender".
If your GPU ("Device ID" on about:support) is not on the whitelist, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender).
If WebRender is not enabled by default for your screen size, but performs well for you, please [file a bug](https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Graphics%3A+WebRender) to request enabling it by default for large screens on Intel/Linux. (If it performs bad, you could file a bug as well. :D bug 1620076 and bug 1617498 will help in the future, but bug 1598380 comment 8 could have caused undetected regressions.)

Back to Bug 1633273 Comment 3