https://bugs.kde.org/show_bug.cgi?id=498181
Gemskip <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Gemskip <[email protected]> --- > Blindly copying what might have improved performance on X11 into a wayland > session isn't the right approach. I'm referring to input latency and not general performance. Not waiting for Vsync probably takes more system resources in general even though it is more responsive. Waiting for Vsync causing latency is pretty universal across operating systems, it is simply disregarded as tearing is less desirable than ~16ms delay for most users. >Kwin not Vsyncing while clients are waiting for frame callbacks would achieve >absolutely nothing anyway. I am not sure how it is implemented, but another Wayland compositor has a forced tearing PR in the works that definitely does improve input responsiveness on 60hz displays and works in windowed applications. The "allow tearing" option in fullscreen games on Kwin achieves a similar improvement in input delay that feels in line with X11. I don't know if this means the compositor is spamming the client with frame callbacks or what, but it feels identical to uncomposited Xorg and very smooth whereas non-tearing situations feel like I am using my computer underwater. >Especially for non-gaming apps. The difference is the same for gaming and non-gaming apps. Gamers speak up about it because for their use case it is unacceptable. -- You are receiving this mail because: You are watching all bug changes.
