You are not logged in.
- Topics: Active | Unanswered
#1 2018-08-24 22:34:51
- archapex
- Member
- Registered: 2018-06-22
- Posts: 8
KDE High Number of Wakeups
I've noticed that my laptop gets a high number of wakeups/second and the CPU hardly reaches sleep state. I thought values above 1000 were normal on idle until I researched that people get within 100-300. I suspect it's mostly KDE related according powertop. I have disabled animations and other effects. But wakeups still remain high, wakeups dropped from 1500 to 1000. I notice that powertop is still finding wakeups from plasmashell and kwin. Any further suggestions?
powrtop
Summary: 1091.1 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 25.7% CPU use
Power est. Usage Events/s Category Description
7.22 W 25.0% Device Display backlight
695 mW 2.1 pkts/s Device Network interface: wlp3s0 (iwlwifi)
52.0 mW 36.7 ms/s 60.4 Process [PID 14568] konsole [kdeinit5]
40.9 mW 21.9 ms/s 136.1 Process [PID 1095] /usr/bin/telegram-desktop -startintray
38.5 mW 29.1 ms/s 21.1 Process [PID 1054] /usr/bin/plasmashell
31.0 mW 20.2 ms/s 57.3 Process [PID 641] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{89ed49f8-13c4-437e-a91c-7cb9b3f40525} -background none -noreset -dis
29.2 mW 18.3 ms/s 63.6 Process [PID 1045] /usr/bin/kwin_x11
28.6 mW 11.6 ms/s 141.3 Interrupt PS/2 Touchpad / Keyboard / Mouse
26.0 mW 6.0 ms/s 186.0 Process [PID 1120] /usr/bin/kwin_x11
20.2 mW 15.5 ms/s 8.3 Process [PID 25861] /usr/bin/ksysguard
16.4 mW 2.9 ms/s 127.8 Timer tick_sched_timer
6.63 mW 4.2 ms/s 14.4 Process [PID 14890] /usr/lib/chromium/chromium --ppapi-flash-version=30.0.0.154 --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplay
5.70 mW 4.2 ms/s 4.8 Timer hrtimer_wakeup
5.53 mW 3.9 ms/s 6.8 Process [PID 25865] /usr/bin/ksysguardd
5.18 mW 3.6 ms/s 7.2 Process [PID 15579] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
4.14 mW 3.3 ms/s 0.3 Process [PID 22406] top
3.84 mW 2.8 ms/s 3.2 Process [PID 14883] /usr/lib/chromium/chromium --ppapi-flash-version=30.0.0.154 --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplay
3.78 mW 2.6 ms/s 4.8 Process [PID 18209] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
3.41 mW 2.2 ms/s 6.3 Interrupt [7] sched(softirq)
3.16 mW 2.2 ms/s 3.7 Process [PID 25780] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
3.05 mW 320.4 µs/s 26.5 Process [PID 10] [rcu_preempt]
2.63 mW 1.7 ms/s 5.4 Process [PID 26007] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
2.51 mW 1.6 ms/s 5.6 Process [PID 15640] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
2.49 mW 1.5 ms/s 5.9 Process [PID 16726] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=2907334752988796441,11572679922329891680,131072 --d
1.99 mW 1.2 ms/s 4.2 Process [PID 28190] powertoptop
top - 00:31:37 up 2 days, 16:46, 5 users, load average: 1.13, 1.15, 1.23
Tasks: 277 total, 1 running, 276 sleeping, 0 stopped, 0 zombie
%Cpu(s): 2.5 us, 1.3 sy, 0.0 ni, 95.6 id, 0.2 wa, 0.3 hi, 0.1 si, 0.0 st
MiB Mem : 7741.7 total, 1018.6 free, 3986.4 used, 2736.7 buff/cache
MiB Swap: 4096.0 total, 3300.8 free, 795.2 used. 3198.0 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1045 stcm 20 0 3149880 57444 30680 S 7.3 0.7 161:56.38 kwin_x11
14568 stcm 20 0 597888 91484 57524 S 5.3 1.2 0:36.97 konsole
641 root 20 0 686476 121644 103568 S 4.0 1.5 113:07.56 Xorg
1054 stcm 20 0 5405620 235932 73532 S 3.3 3.0 167:21.70 plasmashell
25861 stcm 20 0 685080 72580 59864 S 3.0 0.9 0:20.06 ksysguard
1095 stcm 20 0 3304744 220240 50212 S 2.3 2.8 70:43.43 telegram-deskto
25865 stcm 20 0 6316 2168 1968 S 1.0 0.0 0:04.25 ksysguardd
14883 stcm 20 0 1490460 333188 177020 S 0.7 4.2 6:31.61 chromium
15527 stcm 20 0 938336 122084 72828 S 0.7 1.5 0:06.01 chromium
18209 stcm 20 0 988136 174072 76352 S 0.7 2.2 0:21.07 chromium
22406 stcm 20 0 28304 4252 3352 R 0.7 0.1 0:08.85 top
10 root -2 0 0 0 0 I 0.3 0.0 1:35.36 rcu_preempt
1215 stcm 20 0 24476 1848 1672 S 0.3 0.0 0:06.07 dbus-daemon
1318 stcm 20 0 407248 14724 13300 S 0.3 0.2 0:37.79 kuiserver5
15021 stcm 20 0 841468 81300 59836 S 0.3 1.0 0:01.24 chromium
15309 stcm 20 0 924000 118704 71204 S 0.3 1.5 0:04.98 chromium
15579 stcm 20 0 1225012 247116 81644 S 0.3 3.1 0:36.26 chromium
20490 stcm 20 0 930724 122444 70900 S 0.3 1.5 0:05.01 chromium
22745 stcm 20 0 936032 132236 73092 S 0.3 1.7 0:05.67 chromium
25559 stcm 20 0 963108 140876 79640 S 0.3 1.8 0:04.57 chromium
25780 stcm 20 0 1126364 163236 75848 S 0.3 2.1 0:05.40 chromium
26007 stcm 20 0 990688 144028 81404 S 0.3 1.8 0:11.43 chromium
27304 root 20 0 0 0 0 I 0.3 0.0 0:00.33 kworker/u16:1-events_unbound
28447 stcm 20 0 990112 157472 87984 S 0.3 2.0 0:31.45 chromium
29972 root 20 0 0 0 0 I 0.3 0.0 0:00.01 kworker/u16:0-i915
1 root 20 0 224268 5816 3684 S 0.0 0.1 0:06.62 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.32 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-kblockd
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
9 root 20 0 0 0 0 S 0.0 0.0 0:24.35 ksoftirqd/0
11 root -2 0 0 0 0 I 0.0 0.0 0:08.03 rcu_sched
12 root -2 0 0 0 0 I 0.0 0.0 0:00.00 rcu_bh
13 root -2 0 0 0 0 S 0.0 0.0 0:30.52 rcuc/0
14 root -2 0 0 0 0 S 0.0 0.0 0:00.00 rcub/0
15 root rt 0 0 0 0 S 0.0 0.0 0:02.05 migration/0
16 root rt 0 0 0 0 S 0.0 0.0 0:00.30 watchdog/0
17 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
18 root 20 0 0 0 0 S 0.0 0.0 0:00.01 cpuhp/1
19 root rt 0 0 0 0 S 0.0 0.0 0:00.34 watchdog/1
20 root rt 0 0 0 0 S 0.0 0.0 0:00.32 migration/1
21 root -2 0 0 0 0 S 0.0 0.0 0:14.01 rcuc/1
22 root 20 0 0 0 0 S 0.0 0.0 0:09.43 ksoftirqd/1
24 root 0 -20 0 0 0 I 0.0 0.0 0:00.07 kworker/1:0H-kblockd
25 root 20 0 0 0 0 S 0.0 0.0 0:00.01 cpuhp/2
26 root rt 0 0 0 0 S 0.0 0.0 0:00.32 watchdog/2
27 root rt 0 0 0 0 S 0.0 0.0 0:00.33 migration/2
28 root -2 0 0 0 0 S 0.0 0.0 0:13.93 rcuc/2
29 root 20 0 0 0 0 S 0.0 0.0 0:08.89 ksoftirqd/2
31 root 0 -20 0 0 0 I 0.0 0.0 0:00.06 kworker/2:0H-kblockd
32 root 20 0 0 0 0 S 0.0 0.0 0:00.01 cpuhp/3
33 root rt 0 0 0 0 S 0.0 0.0 0:00.35 watchdog/3
34 root rt 0 0 0 0 S 0.0 0.0 0:00.35 migration/3
35 root -2 0 0 0 0 S 0.0 0.0 0:16.41 rcuc/3
36 root 20 0 0 0 0 S 0.0 0.0 0:10.13 ksoftirqd/3 For a brief moment, I noticed this on powertop
1.15 W 46.7 ms/s 799.3 Process [PID 32453] http.so [kdeinit5] https local:/run/user/1000/klauncherZQIcHj.1.slave-socket local:/run/user/1000/plasmashellhbFcANLast edited by archapex (2018-08-24 22:44:59)
Offline
#2 2018-08-25 06:34:17
- seth
- Member
- Registered: 2012-09-03
- Posts: 50,929
Re: KDE High Number of Wakeups
There're quite some input events and I assume telegram might update its systray icon which will wake plasmashell (to repaint the icon) and in turn kwin_x11 (assuming you did not stop the compositor, but "only" disabled fancy trasition events)?
Online
#3 2018-08-26 15:33:03
- archapex
- Member
- Registered: 2018-06-22
- Posts: 8
Re: KDE High Number of Wakeups
Switched off composer and waited for a day, to find a difference. Wakeups still high around 900-1200 on average sometimes drops to 570 for a short time
Summary: 1102.5 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 25.3% CPU use
Power est. Usage Events/s Category Description
6.91 W 100.0% Device Display backlight
1.04 W 3.5 pkts/s Device Network interface: wlp3s0 (iwlwifi)
240 mW 46.5 ms/s 134.3 Process [PID 22337] /usr/lib/chromium/chromium --ppapi-flash-version=30.0.0.154 --ppapi-fl
234 mW 56.2 ms/s 152.8 Process [PID 25686] /usr/lib/chromium/chromium --type=renderer --field-trial-handle=139095
151 mW 24.2 ms/s 124.0 Process [PID 1108] /usr/bin/telegram-desktop -startintray
140 mW 8.1 ms/s 145.0 Interrupt PS/2 Touchpad / Keyboard / Mouse
107 mW 4.3 ms/s 114.3 Process [PID 1123] /usr/bin/kwin_x11
104 mW 3.4 ms/s 113.2 Timer tick_sched_timer
84.0 mW 30.6 ms/s 32.6 Process [PID 678] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{c249a932-baf7-451d-ae76
68.2 mW 12.5 ms/s 21.9 Process [PID 1070] /usr/bin/kwin_x11
43.0 mW 7.5 ms/s 34.0 Process [PID 22344] /usr/lib/chromium/chromium --ppapi-flash-version=30.0.0.154 --ppapi-fl
42.3 mW 10.0 ms/s 26.9 Process [PID 25519] konsole [kdeinit5]
25.9 mW 8.5 ms/s 10.9 Process [PID 1074] /usr/bin/plasmashell
20.3 mW 0.8 ms/s 15.6 Process [PID 1221] /usr/lib/at-spi2-registryd --use-gnome-session
15.3 mW 3.2 ms/s 10.9 Interrupt [7] sched(softirq)
10.4 mW 1.5 ms/s 6.5 Process [PID 1019] kded5 [kdeinit5]
8.60 mW 255.3 µs/s 9.5 Process [PID 10] [rcu_preempt]
8.10 mW 2.5 ms/s 4.0 Process [PID 25554] powertop
7.87 mW 3.5 ms/s 1.7 Timer hrtimer_wakeup
7.30 mW 1.1 ms/s 6.2 Process [PID 8350] konsole [kdeinit5]
6.00 mW 446.8 µs/s 6.0 Process [PID 3437] /usr/bin/dolphin /home/stcm
5.93 mW 480.9 µs/s 5.9 Process [PID 1105] /usr/bin/krunnerOffline
#4 2018-08-26 15:39:42
- seth
- Member
- Registered: 2012-09-03
- Posts: 50,929
Re: KDE High Number of Wakeups
Try to kill telegram.
The only other thing are the input interrupts. Do you only have a touchpad or also a mouse? Can you toggle the touchpad off (many notebooks have a function key to HW disable it)?
Online