| Summary: | Using 60Hz refresh rate on screen capable of 165Hz produces more input lag on Wayland compared to X11 | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | statauskersa33 |
| Component: | input | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | cornerboost, duha.bugs, nate, xaver.hugl |
| Priority: | NOR | Keywords: | efficiency-and-performance, wayland-only |
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | NixOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
statauskersa33
2025-06-23 16:34:13 UTC
I think it would make sense to step back and describe the specific issue you're experiencing here, rather than requesting a bunch of features that may or may not actually fix the issue. The issue is that you experience more input lag on Wayland when using a 60Hz refresh rate, compared to when you do this on X11, right? (In reply to Nate Graham from comment #1) > I think it would make sense to step back and describe the specific issue > you're experiencing here, rather than requesting a bunch of features that > may or may not actually fix the issue. > > The issue is that you experience more input lag on Wayland when using a 60Hz > refresh rate, compared to when you do this on X11, right? Yes. Ok, let's make the bug report about that. (In reply to Nate Graham from comment #1) > I think it would make sense to step back and describe the specific issue > you're experiencing here, rather than requesting a bunch of features that > may or may not actually fix the issue. > > The issue is that you experience more input lag on Wayland when using a 60Hz > refresh rate, compared to when you do this on X11, right? This isn't a bug, this is a feature difference between X11 and Wayland. The monitor refresh cycle on 60hz is long enough (~16ms) that the act of holding back a frame for one or more refresh cycles to make sure they are perfect results in easily humanly discernible lag and is the source of most of the input latency on a standard office PC or laptop. I don't know how much you are buffering, but you are not going to be able to optimize enough to remove the perceptible difference while keeping your frames clean. It is a sacrifice that all modern desktop compositors knowingly make. High-refresh rate monitors just brute-force the problem by having more refreshes. Turning down the display refresh rate saves power almost exclusively by reducing the rate at which the compositor and applications render. Making it render more frames to make up for the lower refresh rate would be nonsensical. Just turn the refresh rate of the display up, implementing global tearing options would not do what you want. X11 works, but somehow when we talk Wayland its impossible. There is no need for walls of text trying to disprove it. On KDE, how to disable "perfect frames" (in other words, how to disable vsync)? |