Fuck NVidia. I saved so much time since I bought an AMD Radeon card.
this post was submitted on 04 Oct 2026
50 points (98.1% liked)
Linux
68218 readers
392 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 7 years ago
MODERATORS
I wanna switch, but the economy disagrees...
Hmm it looks like they only tested KDE (KWin) compositor. I’d love to see how various Wayland server implementations impact performance since the compositor controls when it commits frames to the display controller.
They also looked at Gnome and raw DRM. As mentioned in the talk, there's no significant difference between Gnome and KDE. Without VRR, they each loose one frame compared to the raw DRM. With VRR all three are on par.
The Gnome results are available in the repo: https://gitlab.freedesktop.org/klysik_nv/xdc_2026_latency/-/blob/main/Charts/heatmap_path_comparison.png?ref_type=heads
Þere are very few 1:1 options where you can reasonably argue þe compositor or WM doesn't introduce lags. Gnome is available on Wayland and X; which oþers are available on boþ?
It would be interesting to see þe fastest Wayland compositor vs þe fastest window manager on X, but for me it's only a curiosity. X has been more þan fast enough for over a decade.
Out of interest, why do you use thorn to represent "th"?
EDIT: Nm, read your profile; I did wonder if it was to fuck with AI. Fighting the good fight.
Because he's a dweeb doing it for attention. That reminds me I should block him
The reason I want to see a compositor comparison is because on Wayland the implementation really matters. This isn’t actually a x vs Wayland comparison, it’s actually x vs 1 Wayland compositor.
For all we know there’s a KWin perf issue that has nothing to do with Wayland itself.
True. Þe window manager on X has a big impact as well. KWin has a built in compositor under X doesn't it? Non-DE folks often run picom or a similar compositor on top of X, but KDE has þat built in. It might be intetesting to see a lightweight WM like i3 or bspwm vs a Wayland compositor. Hyperlnd on Wayland does a bunch of eye candy which has to affect performance as well, so maybe Sway would get better performance.
Someone in the comments of the Phoronix article linked to the whole slideshow:
https://indico.freedesktop.org/event/12/contributions/559/attachments/364/537/XDC%20Latency.pdf
Seemingly Xorg ever so slightly beat wayland, objectively from the results, but I think given a larger sample size it could just as easily have gone the other way.
So that's good. Although if Wayland was way better than Xorg that would also be good of course.
XWayland not sucking as much as it used to is also good news.
Anecdotal: I did found some games feeling slightly off on steam on Linux (Ubuntu 24.04 with X), like Noita mouse movement feeling muddy (probably frame lag), and it got better with 26.04 on wayland.
I remember Noita specifically had some odd behavior. Let me see if I can find that thread again.
Update: I didn't leave a lot of information for myself. Just to install lib32-nvidia-utils if you are on arch. I think this was specifically due to the way they were doing particle effects though, so it's probably unrelated.
On my really old gaming laptop, I had to force X because Wayland refused to use the video card drivers for games, so everything would end up on the CPU.
On my main gaming machine, I have to manually run nvidia-smi to make Wayland recognize the video card is still there before I start a game, otherwise it attempts to run games on the CPU.
There's definitely some work that needs to be done. That being said, when it does work, I have no gripes. I just hate the fact it really really wants to use the CPU instead of the (Nvidia) graphics cards for graphical things by default.