| Summary: | System stuttering when GPU nearing 100% | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Zastrix Arundell <zastrixarundell> |
| Component: | performance | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.0.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Frametime when playing elden ring and maxing out the GPU | ||
|
Description
Zastrix Arundell
2024-04-25 23:46:48 UTC
Does this happen only in windowed mode, or in fullscreen too? I tried Red Dead Redemption 2 and Cyberpunk 2077, and while I can make KWin drop tons of frames with RDR2 in windowed mode, that's because compositing takes longer than the frame time with 100% GPU utilization, and no desktop environment can work around that... and in full screen, there are no dropped frames (on KWin's side). Also, can you reproduce this in other games? In the two I tested, even while KWin's dropping frames left and right, that only had a very very minor effect on the game's frame graph. The only games where I reproduced it (which I have and are heavy) is Elden Ring and Witcher 3 non-raytracing. Again, this is a regression in kwin because on KDE5 while I did have this issue originally, I set the compositor to prefer animations and it fixed the issue; the frame were stable when the FPS dropped. On KDE6 there is no such option and I have the original issue. Gnome doesn't have it but I don't like using Gnome. Also while I did not mention it in the previous comment, having the app in fullscreen or not doesn't affect the FPS stuttering. Also this might be an issue for RDNA3 cards... maybe? The GPU clock did seem fine when I test it out, around 3GHz, it might go down to 2.7GHz but it's in that ballpark. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! It does seem to be better in the recent version, there aren't much stutters in the graph now BUT I can see that the <50 FPS situations feel way worse than they should. On GNOME something with ~40FPS feels 40FPS, there's no micro-stuttering in between frames. On KDE I can 100% feel the stuttering. (also dragging windows stuttering, this is on a 7900XTX). I've set my monitor to run @ 60Hz and wither 3 to run on RT Ultra settings, the game is above 60FPS ~(64-68) but it's stuttering even though it's always higher than refresh rate of my monitor. This is also happening in the Elder Scrolls Online when FPS is uncapped, so it's not a ray-tracing issue. Generally since 6.0.4 I didn't have this issue that much. Gnome handles lower frame rates a bit better now but that's something you need VRR for either way in the context of gaming. I'd guess the issue can be closed now. Yeah with 6.0.4(.1) you're much more likely to hit direct scanout because there was a bug in it before. It almost certainly was that... if the issue comes back though, just reopen this. |