https://bugs.kde.org/show_bug.cgi?id=452119
kde@grau.net changed:
What|Removed |Added
CC||kde@grau.net
--- Comment #11 from kde
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #12 from kde@grau.net ---
Created attachment 148637
--> https://bugs.kde.org/attachment.cgi?id=148637&action=edit
sudo intel_gpu_top > x11-moving-window.log
Output of intel_gpu_top for a window being moved on an X11 desktop
--
You ar
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #13 from kde@grau.net ---
Created attachment 148638
--> https://bugs.kde.org/attachment.cgi?id=148638&action=edit
sudo intel_gpu_top > wayland-idle.log
Output of intel_gpu_top for an idle Wayland desktop
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #14 from kde@grau.net ---
Created attachment 148640
--> https://bugs.kde.org/attachment.cgi?id=148640&action=edit
sudo intel_gpu_top > wayland-moving-window.log
Output of intel_gpu_top for a window being moved on a Wayland desktop
--
https://bugs.kde.org/show_bug.cgi?id=452119
kde@grau.net changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #16 from kde@grau.net ---
(In reply to Zamundaaa from comment #9)
> I don't know how to check the memory clock on Intel systems, searching for
> it doesn't yield results for the dynamic memory speed either.
>
> We can just check for it d
https://bugs.kde.org/show_bug.cgi?id=452119
Lemmiwinks changed:
What|Removed |Added
CC||a.lem...@posteo.de
--- Comment #18 from Lemmiwinks
https://bugs.kde.org/show_bug.cgi?id=452119
John changed:
What|Removed |Added
CC||ilikef...@waterisgone.com
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=452119
Podagric changed:
What|Removed |Added
CC||kde.podag...@slmail.me
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #17 from Zamundaaa ---
Integrated GPUs do very much influence the used memory frequency, it has a
large effect on performance and battery life.
But glxgears running should already put memory frequency to the maximum, it
certainly does that o
https://bugs.kde.org/show_bug.cgi?id=452119
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--- Comment #1 from Patrick
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #2 from Patrick Silva ---
My versions:
Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Celer
https://bugs.kde.org/show_bug.cgi?id=452119
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #3 from Zamundaaa ---
> But what REALLY helps, is enabling the Show FPS effect
Does the GPU or memory clock go up if you enable it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #4 from Antonio Orefice ---
(In reply to Zamundaaa from comment #3)
> > But what REALLY helps, is enabling the Show FPS effect
>
> Does the GPU or memory clock go up if you enable it?
If I remember right, it goes from 2mhz to about 200mhz.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #5 from Antonio Orefice ---
(In reply to Zamundaaa from comment #3)
> > But what REALLY helps, is enabling the Show FPS effect
>
> Does the GPU or memory clock go up if you enable it?
Enabling show fps effects bump the gpu use to about 150
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #6 from Zamundaaa ---
What does the memory clock do with the fps effect? GPU core clock is not the
single deciding factor on performance
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #7 from Antonio Orefice ---
(In reply to Zamundaaa from comment #6)
> What does the memory clock do with the fps effect? GPU core clock is not the
> single deciding factor on performance
If you are asking me, I've no idea.
I answered to you
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #8 from Antonio Orefice ---
Aye, i've read better, sorry.
I don't know how to read current memory clock speed. Do you have advices?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #9 from Zamundaaa ---
I don't know how to check the memory clock on Intel systems, searching for it
doesn't yield results for the dynamic memory speed either.
We can just check for it differently though: If you start glxgears and leave
that
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #10 from Antonio Orefice ---
(In reply to Zamundaaa from comment #9)
> I don't know how to check the memory clock on Intel systems, searching for
> it doesn't yield results for the dynamic memory speed either.
>
> We can just check for it d
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #19 from Nate Graham ---
I was experiencing this issue and found that the cause was actually Firefox
forcing kwin to constantly repaint the screen; see
https://bugzilla.mozilla.org/show_bug.cgi?id=1754810. Setting
`widget.wayland.vsync.enabl
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #20 from Lemmiwinks ---
(In reply to Nate Graham from comment #19)
> I was experiencing this issue and found that the cause was actually Firefox
> forcing kwin to constantly repaint the screen; see
> https://bugzilla.mozilla.org/show_bug.cgi
https://bugs.kde.org/show_bug.cgi?id=452119
Pawel changed:
What|Removed |Added
CC||bednarczyk.pa...@outlook.co
|
https://bugs.kde.org/show_bug.cgi?id=452119
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=452119
George Melikov changed:
What|Removed |Added
CC||m...@gmelikov.ru
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #21 from Zamundaaa ---
Can everyone that's affected attach the output of drm_info
(https://gitlab.freedesktop.org/emersion/drm_info) on their system?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #22 from Patrick Silva ---
Created attachment 153392
--> https://bugs.kde.org/attachment.cgi?id=153392&action=edit
output of drm_info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #23 from Zamundaaa ---
Ok. Can you check if any of these environment variables (only one at a time)
make a difference?
KWIN_DRM_NO_AMS=1
KWIN_DRM_USE_MODIFIERS=0
KWIN_DRM_PREFER_COLOR_DEPTH=24
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #24 from Lemmiwinks ---
Created attachment 153395
--> https://bugs.kde.org/attachment.cgi?id=153395&action=edit
output of drm_info (Haswell-ULT Integrated Graphics Controller (rev 0b))
Here is my output of drm_info. Going to check your su
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #25 from Podagric ---
Created attachment 153399
--> https://bugs.kde.org/attachment.cgi?id=153399&action=edit
drm_info (HD Intel® 4600)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #26 from Podagric ---
(In reply to Zamundaaa from comment #23)
> Ok. Can you check if any of these environment variables (only one at a time)
no difference
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #27 from Zamundaaa ---
I'm afraid this will need to be brute forced then; if performance was fine in
5.18 but not now then a bisect would be useful. As that's pretty much
impossible to do over such a large range of versions, can you boot a f
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #28 from Patrick Silva ---
I have tested the env variables by adding them to /env/environment file. Plasma
animations are more fluid when I use the first two options, but video playback
with mpv, vlc and gstreamer-based players is still stut
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #29 from Patrick Silva ---
And kwin_wayland crashed once when I minimized a window with click on the task
manager while using KWIN_DRM_USE_MODIFIERS=0
Thread 12 (Thread 0x7f15968976c0 (LWP 3945)):
#0 0x7f15ed921096 in epoll_wait (epf
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #30 from Zamundaaa ---
That's the same backtrace as bug 460563, it shouldn't be related to the
performance problem though.
(In reply to Patrick Silva from comment #28)
> I have tested the env variables by adding them to /env/environment fil
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #31 from Patrick Silva ---
Created attachment 153404
--> https://bugs.kde.org/attachment.cgi?id=153404&action=edit
drm_info_output of celeron g1820 haswell
(In reply to Zamundaaa from comment #30)
> That's the same backtrace as bug 460563
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #32 from Zamundaaa ---
Thanks. Can you also attach the output of drm_info with the
KWIN_DRM_USE_MODIFIERS=0 env var set?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #33 from Patrick Silva ---
Created attachment 153405
--> https://bugs.kde.org/attachment.cgi?id=153405&action=edit
drm_info output with the KWIN_DRM_USE_MODIFIERS=0 env var set
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #34 from Zamundaaa ---
On your hardware Mesa chooses the same buffer format and layout with and
without modifiers. That's quite unexpected, there's nothing here that could
cause a difference in performance
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #35 from Podagric ---
I tested the wayland section of gnome on my hardware and had performance
problems just like with plasma.
Searching a bit more I saw that there is a version of mutter with a patch to
enable the tripple buffer, and after
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #36 from Lemmiwinks ---
Created attachment 153497
--> https://bugs.kde.org/attachment.cgi?id=153497&action=edit
output of drm_info on wayland (Haswell-ULT Integrated Graphics Controller (rev
0b))
This is my drm_info output on Wayland, the
https://bugs.kde.org/show_bug.cgi?id=452119
Rean changed:
What|Removed |Added
CC||tech...@protonmail.com
--- Comment #45 from Rean ---
I'
https://bugs.kde.org/show_bug.cgi?id=452119
Andrey changed:
What|Removed |Added
CC||butir...@gmail.com
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #46 from Lemmiwinks ---
I think I made an observation: under System Settings -> Compositor, setting the
latency to "force smoothest animations", seems to almost fix the problem for
me. Maybe someone could try this...
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #47 from Antonio Orefice ---
(In reply to Lemmiwinks from comment #46)
> I think I made an observation: under System Settings -> Compositor, setting
> the latency to "force smoothest animations", seems to almost fix the problem
> for me. May
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #48 from Nate Graham ---
Git commit cf583aa3673cfca275b64d25c457d9e4a298c46c by Nate Graham, on behalf
of Vlad Zahorodnii.
Committed on 17/01/2023 at 04:10.
Pushed by ngraham into branch 'master'.
Change default latency policy to "Force smo
https://bugs.kde.org/show_bug.cgi?id=452119
Vlad Zahorodnii changed:
What|Removed |Added
CC||liubomi...@gmail.com
--- Comment #49 from Vla
https://bugs.kde.org/show_bug.cgi?id=452119
Andrew Gunnerson changed:
What|Removed |Added
CC||accounts+...@chiller3.com
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=452119
Vlad Zahorodnii changed:
What|Removed |Added
CC||tro...@free.fr
--- Comment #50 from Vlad Zaho
https://bugs.kde.org/show_bug.cgi?id=452119
Joshua T changed:
What|Removed |Added
CC||joshuaandre...@gmail.com
--- Comment #37 from Joshua
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #38 from Antonio Orefice ---
(In reply to Joshua T from comment #37)
> I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issues
> on my Intel UHD 600. Animations were very close to 60 FPS. I have definitely
> seen this prob
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #39 from Lemmiwinks ---
(In reply to Joshua T from comment #37)
> I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issues
> on my Intel UHD 600. Animations were very close to 60 FPS. I have definitely
> seen this problem i
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #40 from Joshua T ---
(In reply to Antonio Orefice from comment #38)
> (In reply to Joshua T from comment #37)
> > I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issues
> > on my Intel UHD 600. Animations were very close
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #41 from Joshua T ---
(In reply to Lemmiwinks from comment #39)
> (In reply to Joshua T from comment #37)
> > I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issues
> > on my Intel UHD 600. Animations were very close to 6
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #42 from Antonio Orefice ---
(In reply to Joshua T from comment #40)
> (In reply to Antonio Orefice from comment #38)
> > (In reply to Joshua T from comment #37)
> > > I just tried Fedora KDE Rawhide with Wayland, and I didn't have any issue
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #43 from Lemmiwinks ---
I can confirm that using the Show FPS effect makes the whole situation a lot
better.
Could it be that there is some kind of CPU/GPU frequency scaling error?
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=452119
--- Comment #44 from Joshua T ---
I used the show FPS effect to get evidence of the performance of wayland vs
xorg. The effect didn’t improve the performance in any way for me. Wayland on
Fedora 38 KDE was still smooth before enabling the effect.
--
Y
58 matches
Mail list logo
