Another post suspects Nvidia drivers: https://davidjusto.com/articles/m2p-latency/#results
replyOh yes, that makes a lot of sense.
replyYep, OP should certainly retest under gnome. Im not in the weeds myself but I get the vibe that gnome's wayland compositor is somewhat faster and more carefully designed than kwin (at least, Emacs in pgtk mode does substantially better under gnome, whereas on Kwin it uses substantial cpu when scrolling and even lags a bit at high resolutions)
replyThis is an annoying style of argument from Wayland fans.
replyWayland fan: You need to switch to Wayland. X is deprecated and has been for years! Wayland is the future.
User: Okay, I tried, and it's broken/worse.
Wayland fan: No, you don't understand, Wayland is just a protocol. It's your implementation of Wayland that is at fault, not Wayland itself! Wayland is still great!
User: But X was working fine...
Is this some kind of Pavlov's dog reaction? That's not what my comment was about, and even if it was it wouldn't make any sense anyway as KWin had good results in these measurements.
replyIt's exactly what your comment was about: the same boring motte and bailey fallacy of “you don't understand, wayland is a protocol”
replyIf your protocol you pushed to replace a working implementation invites a dozen poor implementations which people routinely confuse, that's a problem with the protocol and the push to get people to use it.
Looks like this pavlovian reaction is quite widespread. It's baffling how can you so confidently miss the point.
reply