You are not logged in.

#1 2024-02-23 22:53:08

Fullsteam
Member
Registered: 2022-08-25
Posts: 23

(solved)norm cpu usage for kwin under wayland failed wayland session?

Hi there

I recently setup plasma under wayland and have been noticing CPU usage hitting 15 - 20% reported as coming from Plasma shell/kwin (according to Htop) also some cpu spikes from applications like chrome to 50% with light load is this normal
also while Wayland works fine with some graphical glitchiness apparently it opens a second wayland plasma session on tty2 with just a black screen and cursor


Software
_________________
KDE Plasma Version : 5.27.10
KDE Frameworks Version: 5.115.0
QT Version : 5.15.12
Kernel Version : 6.6.18-1-lts (64-bit)
Nvidia driver : 545.29.06-20 from the main repository

Hardware
___________________
AMD Ryzen 9 5950X
32 GB ram
Nvidia RTX 2080 super

Last edited by Fullsteam (2024-03-05 02:32:16)

Offline

#2 2024-02-23 22:56:24

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,480
Website

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Fullsteam wrote:

CPU usage hitting 15 - 20% reported as coming from Wayland (according to Htop)

Ah, what??  There is no "Wayland" binary to run or be reported in htop.  Do you mean plasma?  Or what?


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2024-02-23 23:05:07

Fullsteam
Member
Registered: 2022-08-25
Posts: 23

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Yeah sorry trilby you're right plasma shell/kwin

Offline

#4 2024-02-24 02:22:08

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,267

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Are you running in software on the llvmpipe device? Post

qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation

do you have any cpu/resource monitoring widgets/plasmoids active? They've historically been the casue for higher CPU usage, might want to disable those

Offline

#5 2024-02-24 05:52:51

Fullsteam
Member
Registered: 2022-08-25
Posts: 23

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Hi V1del

thanks for the response this was the result from the command

 Version
=======
KWin version: 5.27.10
Qt Version: 5.15.12
Qt compile version: 5.15.12
XCB compile version: 1.16

Operation Mode: Xwayland

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12302004
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Plugin recommends border size: None
onAllDesktopsAvailable: false
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 6, 3, 4, 5
borderSize: 0
gridUnit: 10
font: Noto Sans,10,-1,0,50,0,0,0,0,0
smallSpacing: 2
largeSpacing: 10

Output backend
==============
Name: DRM
Active: true
Atomic Mode Setting on GPU 0: true

Cursor
======
themeName: breeze_cursors
themeSize: 24

Options
=======
focusPolicy: 0
xwaylandCrashPolicy: 
xwaylandMaxCrashCount: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 0
delayFocusInterval: 0
shadeHover: false
shadeHoverInterval: 250
separateScreenFocus: false
activeMouseScreen: true
placement: 
activationDesktopPolicy: 0
focusPolicyIsReasonable: true
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: false
focusStealingPreventionLevel: 1
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 28
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 28
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 28
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777250
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
compositingMode: 1
useCompositing: true
hiddenPreviews: 1
glSmoothScale: 2
glStrictBinding: false
glStrictBindingFollowsDriver: true
glPreferBufferSwap: 99
glPlatformInterface: 2
windowsBlockCompositing: true
latencyPolicy: 
renderTimeEstimator: 
allowTearing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Active screen follows mouse:  yes
Number of Screens: 2

Screen 0:
---------
Name: DP-1
Enabled: 1
Geometry: 2560,0,2560x1440
Scale: 1
Refresh Rate: 143973
Adaptive Sync: incapable
Screen 1:
---------
Name: DP-3
Enabled: 1
Geometry: 0,0,2560x1440
Scale: 1
Refresh Rate: 144000
Adaptive Sync: incapable

Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 545.29.06
OpenGL platform interface: EGL
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 545.29.6
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
Linux kernel version: 6.6.18
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used

Loaded Effects:
---------------
colorpicker
outputlocator
screenshot
screenedge
zoom
blur
contrast
kwin4_effect_sessionquit
kwin4_effect_logout
kwin4_effect_login
slidingpopups
kwin4_effect_windowaperture
slide
kwin4_effect_fadingpopups
kwin4_effect_maximize
kwin4_effect_morphingpopups
kwin4_effect_squash
kwin4_effect_fullscreen
kwin4_effect_frozenapp
kwin4_effect_scale
kwin4_effect_dialogparent
desktopgrid
highlightwindow
overview
tileseditor
windowview
blendchanges
startupfeedback
kscreen
screentransform

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
colorpicker:

outputlocator:

screenshot:

screenedge:

zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
focusTrackingEnabled: false
textCaretTrackingEnabled: false
focusDelay: 350
moveFactor: 20
targetZoom: 1

blur:

contrast:

kwin4_effect_sessionquit:
pluginId: kwin4_effect_sessionquit
isActiveFullScreenEffect: false

kwin4_effect_logout:
pluginId: kwin4_effect_logout
isActiveFullScreenEffect: false

kwin4_effect_login:
pluginId: kwin4_effect_login
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 150
slideOutDuration: 250

kwin4_effect_windowaperture:
pluginId: kwin4_effect_windowaperture
isActiveFullScreenEffect: false

slide:
horizontalGap: 45
verticalGap: 20
slideBackground: true

kwin4_effect_fadingpopups:
pluginId: kwin4_effect_fadingpopups
isActiveFullScreenEffect: false

kwin4_effect_maximize:
pluginId: kwin4_effect_maximize
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
pluginId: kwin4_effect_morphingpopups
isActiveFullScreenEffect: false

kwin4_effect_squash:
pluginId: kwin4_effect_squash
isActiveFullScreenEffect: false

kwin4_effect_fullscreen:
pluginId: kwin4_effect_fullscreen
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
pluginId: kwin4_effect_frozenapp
isActiveFullScreenEffect: false

kwin4_effect_scale:
pluginId: kwin4_effect_scale
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
pluginId: kwin4_effect_dialogparent
isActiveFullScreenEffect: false

desktopgrid:
activeView: 
gridRows: 1
gridColumns: 1
animationDuration: 300
layout: 1
partialActivationFactor: 0
gestureInProgress: false
showAddRemove: true
desktopNameAlignment: 0
desktopLayoutMode: 0
customLayoutRows: 2

highlightwindow:

overview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
blurBackground: true
partialActivationFactor: 0
gestureInProgress: false
searchText: 

tileseditor:
activeView: 
animationDuration: 200

windowview:
activeView: 
animationDuration: 300
layout: 1
ignoreMinimized: false
mode: 97189968
partialActivationFactor: 0
gestureInProgress: false
searchText: 

blendchanges:

startupfeedback:
type: 1

kscreen:

screentransform:


Loaded Plugins:
---------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast

Available Plugins:
------------------
kwin5_plugin_buttonrebinds
kwin5_plugin_colord
kwin5_plugin_krunner
kwin5_plugin_nightcolor
kwin5_plugin_screencast 

I noticed opengl platform listed as EGL i'm thinking like eglstreams as opposed to GBM which i have enforced through the enviroment variable is this a problem?
Also i'm not sure about many monitoring tools i have one on my desktop for individual core usage but nothing else.

also sometimes when i click on my start menu or the menu for things like vaults and other utilities not on the default bar the menus won't pop up

I admit i'm partly just going have  i set this up correctly because the setup guides i found are quite small and i'm not sure if there is more i need to do beyond what they say.
setup Guides being
https://wiki.archlinux.org/title/Wayland
https://community.kde.org/Plasma/Wayland/Nvidia

Thank you for all help on this

Offline

#6 2024-02-24 06:03:57

Fullsteam
Member
Registered: 2022-08-25
Posts: 23

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Yep and apparently sddm i think it is opening 2 plasma tty sessions and then when sddm is restarted it stops the failed? session on tty2 but leaves a broken session on tty1 i think
don't know if thats normal

Offline

#7 2024-02-24 07:59:40

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,547

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

kwin doesnt support eglstreams  and neither are you using that nor llvmpipe

also sometimes when i click on my start menu or the menu for things like vaults and other utilities not on the default bar the menus won't pop up

If you want to try plasma on wayland you likely want to go w/ the kde-unstable version - or wait.

apparently sddm i think it is opening 2 plasma tty sessions and then…

SDDM doesn't "think" - please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

Offline

#8 2024-03-04 22:58:13

Fullsteam
Member
Registered: 2022-08-25
Posts: 23

Re: (solved)norm cpu usage for kwin under wayland failed wayland session?

Apologies for the late response on this i suppose i'm used to running on a much tighter performance budget on a 3600x so i spooked when i saw core usage spike to 100%
In regards to the failed plasma session (black screen with just a cursor) which is the same thing i got when running egl streams not gdm it appears its because sddm will launch that session but its a placeholder? or fails? so when sddm is restarted the second screen on tty1 with a successful session will not shutdown.

On the basis of what Seth said i want stability so i transitioned back to xorg for the time being i hope to use wayland more in the future as its awesome.

Thank you very much to everyone who helped me in this thread

Offline

Board footer

Powered by FluxBB