You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed sway always seemed to be appearing in top. I ran top -n 10 -b > /tmp/toplog to have top output to a file, and then didn't move the mouse or press anything on the keyboard. I even customized kitty with cursor_blink_interval 0 so that not a single pixel on any of my outputs would be changing. But sway kept using ~8% CPU the whole time. This seems like it could be a noticeable hit for battery life. Maybe doing something on a timer? This is my first time using wayland so I don't know if this is expected for wayland compositors, but my X window managers definitely did not do this. I think even the X server didn't as long as no pixels were changing but my memory of that is fuzzier.
The text was updated successfully, but these errors were encountered:
Please fill out the following:
Sway Version: 1.9
Debug Log:
sway.log
strace.log
Configuration File:
sway.conf.txt
Description:
top -n 10 -b > /tmp/toplog
to have top output to a file, and then didn't move the mouse or press anything on the keyboard. I even customized kitty withcursor_blink_interval 0
so that not a single pixel on any of my outputs would be changing. But sway kept using ~8% CPU the whole time. This seems like it could be a noticeable hit for battery life. Maybe doing something on a timer? This is my first time using wayland so I don't know if this is expected for wayland compositors, but my X window managers definitely did not do this. I think even the X server didn't as long as no pixels were changing but my memory of that is fuzzier.The text was updated successfully, but these errors were encountered: