https://bugs.kde.org/show_bug.cgi?id=490358
Michael Marley changed:
What|Removed |Added
CC||mich...@michaelmarley.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=490358
David Edmundson changed:
What|Removed |Added
Component|compositing |performance
CC|
https://bugs.kde.org/show_bug.cgi?id=490358
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #2 from Michael Marley ---
That doesn't seem to have any effect; I still get the framerate slowdowns and
frame drops.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490358
Michael Marley changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=490358
Zamundaaa changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=490358
Michael Marley changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #6 from Zamundaaa ---
Is that even with KWIN_DRM_DISABLE_TRIPLE_BUFFERING=1, or only without it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #7 from Michael Marley ---
It happens no matter whether I disable triple buffering or not. There doesn't
seem to be any difference between modes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #8 from Zamundaaa ---
Okay, then please set KWIN_LOG_PERFORMANCE_DATA=1, reboot and upload the .csv
file with performance data KWin creates in your home folder after triggering
the stutter for a bit.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #9 from Michael Marley ---
Created attachment 171989
--> https://bugs.kde.org/attachment.cgi?id=171989&action=edit
KWin performance statistics during display stuttering
Sure, here's the CSV file. While capturing this data, I started the
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #10 from Zamundaaa ---
hmm, effectively all dropped frames are because of late commits, which means
KWin's missing some deadlines on the CPU side.
When you start the apps, does that perhaps come with a bunch of CPU usage?
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #11 from Michael Marley ---
Created attachment 172006
--> https://bugs.kde.org/attachment.cgi?id=172006&action=edit
KWin performance statistics during display stuttering at lower CPU load
Good point, the CPU usage is rather high during th
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #12 from Michael Marley ---
For what it is worth, I also tried it with the "performance" CPU governor and I
see no difference in the frame drops.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #13 from Zamundaaa ---
It has half the dropped frames, so that's something at least.
> and started typing in IntelliJ, which also reproduces the frame drops
That probably does autocomplete predictions, which do take some CPU
temporarily. If
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #14 from Michael Marley ---
Sure, I can do that. Do you have a suggestion on what value I should try, or
should I just increase it until I don't see any more frame drops?
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #15 from Michael Marley ---
I ended up trying a few different values. I started by doubling it to 3000us,
which had no effect. I then doubled it again to 6000us, which had very little
or no effect. I then used 15003us, which is, assuming
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #16 from Michael Marley ---
I've done quite a bit more testing and I have made some interesting and
hopefully-relevant findings. After determining that raising the safetyMargin
to 15003ms eliminated most of the frame drops, I then attempted
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #17 from Michael Marley ---
(When I said 15003ms, I actually meant 15003us, sorry.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #18 from Michael Marley ---
I just made a startling discovery. The kwin packaging for Debian/Ubuntu (which
I had been using all along) doesn't set CAP_SYS_NICE on kwin_wayland, so the
attempt to set a higher priority for the input and outpu
https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #19 from Zamundaaa ---
Okay, that's good. I mean, it's not good that you need a safety margin of 3ms,
but I think it's possible to detect that with some generic code in KWin.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=490358
pallaswept changed:
What|Removed |Added
CC||pallasw...@proton.me
--
You are receiving this ma
22 matches
Mail list logo
