https://bugs.kde.org/show_bug.cgi?id=485609
--- Comment #6 from cantf...@gmail.com --- Ok, I have rechecked using live Neon stable: Palsma 6.3.4 KDE Frameworkd 6.13.0 Qt 6.8.3 Kernel 6.11.0-24 There's some improvement when the mouse is moved over KDE applications (e.g. Dolphin, Konsole, Okular, the desktop) - kwin_wayland uses ~30% a core for that now instead of 100%. But if the mouse if moved over Firefox (blank area in the default Firefox homepage) - kwin_wayland uses 100% of a core, and firefox-bin uses ~50% of a core. Gimp and bitwarden use xwayland for some reason, and there kwin_wayland was similar to KDE applications. Moving to X11, CPU usage was still lower across the board. kwin_x11 uses about a quarter of what kwin_wayland uses on KDE applications, firefox_bin still uses the same amount of CPU, but kwin_x11 doesn't use lots of CPU as opposed to kwin_wayland in this scenario either. In short - it got better for most applications I have tested - but X11 was still noticeably more efficient in CPU usage. -- You are receiving this mail because: You are watching all bug changes.
