There is no advantage to games and average applications preferring Wayland over X11 – only severe performance and unusability regressions right now. Thus, we must revert this change until fifo-v1 and commit-timing-v1 are released and at least in a stable release for major compositors."
Does this mean I’ve been getting reduced performance for using Wayland when playing games? I haven’t noticed any difference but I haven’t been benchmarking.
It’s always felt just a tiny bit better for me, but also never benchmarked it. Maybe on particularly heavy workloads or less powerful devices like the Steam Deck. Could also be that Gamescope doesn’t cope too well with it.
I do have 2 GPUs, one for my displays and desktop another dedicated to compute/VMs/gaming. So I wouldn’t know if it causes the compositor to slow down or starve for GPU access, as the game has a whole GPU just for itself.
Does this mean I’ve been getting reduced performance for using Wayland when playing games? I haven’t noticed any difference but I haven’t been benchmarking.
No.
It’s always felt just a tiny bit better for me, but also never benchmarked it. Maybe on particularly heavy workloads or less powerful devices like the Steam Deck. Could also be that Gamescope doesn’t cope too well with it.
I do have 2 GPUs, one for my displays and desktop another dedicated to compute/VMs/gaming. So I wouldn’t know if it causes the compositor to slow down or starve for GPU access, as the game has a whole GPU just for itself.