I don't think that results can be significantly faster because obviously it is already limited by resources. But less compositing layers gives lower latency and I suspect those numbers increase thanks to higher minimum FPS. It is even noticeable with Plasma 5.21 on Xorg which has kwin latency adjustment setting. It would be interesting to test one game/app but gather numbers like min/avg/max/95pct etc. - similar to what gaming sites are doing.
Announcement
Collapse
No announcement yet.
Ubuntu 21.04 - X.Org vs. Wayland Linux Gaming Performance
Collapse
X
-
Originally posted by QwertyChouskie View PostIt's amazing how boring this transition is looking. Once AutoKey is working on Wayland (and I figure out how to disable my broken, ghost-touching touchscreen on a Wayland session), I'm definitely going to attempt the switch.
Classification: Enhancement Reproducibility: Always Summary By default Gnome use Wayland, but looks like Autokey supports only x.org Steps to Reproduce Run Autokey in Gnome (with Wayland as backend...
AutoKey current version applications running in XWayland on top of Wayland can be controlled. So depending on how you use AutoKey you might be their already.
https://github.com/snyball/Hawck is another interesting one to watch as it can control TTYs as well as graphical.
Comment
-
It should be mentioned that unfortunately there's still the issue that if the hardware does not keep up with refresh rate, mouse movement is still throttled to the frame rate - i.e. if the game runs at 40fps on a 60Hz screen, you will notice mouse stuttering. It will hopefully fixed in Gnome 41 - it's not Wayland specific, just a Mutter implementation detail.
That said, I'd expect the biggest performance differences between X11/Xwayland vs native Wayland to show once franctional scaling is properly figured out. On Wayland, it's possible to do it without performance loss.
- Likes 4
Comment
-
Most other Linux experts remain skeptical about Wayland; Canonical, Red Hat, etc. Fedora is alone with these new untested technologies, including BTRFS.
Wayland needs testing on upscale and downscaling to different display sizes, different & multiple screen sizes, etc. It should be expected that many applications will be very troublesome with Wayland, for several more months.
Both GNOME & Wayland differ from most Linux additions. Only complex modifications can be made before being usable. When Canonical & most others use GNOME, few like the GNOME defaults. Luckily this latest version of GNOME is not such a major deviation from the expected WIMP formula created by Xerox.
Later versions of the official Linux kernels might make these Linux innovations easier. "The Linux Foundation" has so many integration tasks ahead, with Wayland, BTRFS, etc.Last edited by gregzeng; 29 April 2021, 08:54 PM.
- Likes 1
Comment
-
Originally posted by gregzeng View PostMost other Linux experts remain skeptical about Wayland; Canonical, Red Hat, etc. Fedora is alone with these new untested technologies, including BTRFS.
Wayland needs testing on upscale and downscaling to different display sizes, different & multiple screen sizes, etc. It should be expected that many applications will be very troublesome with Wayland, for several more months.
Both GNOME & Wayland differ from most Linux additions. Only complex modifications can be made before being usable. When Canonical & most others use GNOME, few like the GNOME defaults. Luckily this latest version of GNOME is not such a major deviation from the expected WIMP formula created by Xerox.
Later versions of the official Linux kernels might make these Linux innovations easier. "The Linux Foundation" has so many integration tasks ahead, with Wayland, BTRFS, etc.
Debian 10 released July 2019 with gnome desktop was defaulting to Wayland over X11 using AMD or Intel graphics. Same is true with RHEL 8 released in 2019.
Sorry to say a lot of Linux experts making distributions have been setting the default to be Wayland progressively more and more.
The writing was on the wall about wayland coming in 2019 as the core distributions that most distributions are based on started defaulting to wayland for their primary desktop environments.
We are almost 2 years in to the conversion over to Wayland over X11.
Originally posted by gregzeng View PostWayland needs testing on upscale and downscaling to different display sizes, different & multiple screen sizes, etc.
- Likes 11
Comment
-
Originally posted by skeevy420 View PostI like how, aside from the one game, the Wayland performance seemed better if only by a slight hair. To me, minimal FPS and and frame rate are the more important numbers so it's nice seeing XWayland having slightly better numbers even if it isn't by much.
Since I've been gaming on Xorg KDE and Windows lately -- Can anyone comment on how input feels on Wayland? I assume it's nice and snappy. PS4 BT Input lag is my biggest worry when the Wayland transition finally happens on my system.
- Likes 1
Comment
-
Originally posted by oiaohm View Post
Really the Most other Linux experts. https://wiki.debian.org/Wayland#Supported_environments.
Debian 10 released July 2019 with gnome desktop was defaulting to Wayland over X11 using AMD or Intel graphics. Same is true with RHEL 8 released in 2019.
Sorry to say a lot of Linux experts making distributions have been setting the default to be Wayland progressively more and more.
The writing was on the wall about wayland coming in 2019 as the core distributions that most distributions are based on started defaulting to wayland for their primary desktop environments.
We are almost 2 years in to the conversion over to Wayland over X11.
There is something important here. x.org setup for doing this testing is now only used for testing XWayland and Wayland technologies. Yes Redhat only putting forward a maintainer for XWayland not X11 on bare metal is a big huge change. Going forwards X11 on bare metal having issues with different display sizes is a real risk due to no maintainer and no testing framework to detect those faults.
- Likes 2
Comment
Comment