river icon indicating copy to clipboard operation
river copied to clipboard

Published 20 hours ago • verified publisher icon riverwm

High idle CPU usage with wayvnc

Open chcore opened this issue 2 years ago • 1 comments

When running river, wayvnc consistently uses 30-40% of a CPU core when no VNC clients are even connected. For comparison, CPU usage under the same conditions is negligible when running Sway.

I am experiencing this on two different machines. Is this happening to anybody else? I would expect the load to be very low, if not nothing, while no clients are connected.

chcore avatar Aug 09 '22 05:08 chcore

Likely related to river not doing full damage tracking yet.

Leon-Plickat avatar Aug 11 '22 04:08 Leon-Plickat

You may be onto something, the CPU usage is similarly high when there is a lot of "damage" when using sway (again, when no clients are connected). I might raise a wayvnc issue for this.

chcore avatar Aug 17 '22 11:08 chcore

Thanks Leon-Plickat.

Worked around the issue by having wayvnc run only when needed via systemd socket activation. Hoping #206 will be implemented soon.

chcore avatar Aug 18 '22 04:08 chcore