Shadow-server: 2019-04-03 11:40:49,790 xpra GTK2 shadow version 2.5-r22096 64-bit 2019-04-03 11:40:49,794 running with pid 18889 on Linux Ubuntu 16.04 xenial ========== Client: set "XPRA_EXECUTABLE=C:\Users\stavros.ntentos\Documents\xpra-clients\Xpra-Client-Python3-x86_64_2.5-r22135" 2019-04-03 11:40:51,056 Python/GTK3 Microsoft Windows 10 aero client version 2.5-r22135 64-bit
Xpra-Client-Python3-x86_64_2.5-r22135\xpra_cmd" shadow ssh://user@ip/0 --clipboard=no --opengl=no --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off
Which is also weird percentage, since I have an i7-3540M (4 logical cores) which means 1-and-8% processors
I am not sure what else to report :/ shadow server was doing "basic stuff" (move mouse and workspaces around etc) and collecting again debugs for #2249
Can you try to change the refresh delay (in milliseconds):
XPRA_SHADOW_REFRESH_DELAY=200 xpra shadow :0
To see if the CPU usage is related to the refresh rate.
From your log I see:
Xpra GTK2 shadow server version 2.5-r22096 64-bit
That's older than 2.5 final, why is that?
Replying to Antoine Martin:
From your log I see:
Xpra GTK2 shadow server version 2.5-r22096 64-bitThat's older than 2.5 final, why is that?
No idea :/ as per #2246 I only had whatever this
/etc/apt$ grep -TrinP 'xpra|winswitch' sources.list.d/xpra.list.save: 1 :deb https://xpra.org/beta/ xenial main sources.list.d/xpra.list: 1 :deb https://xpra.org/beta/ xenial main
gave me as the latest package (I run apt-get update
quite frequently).
I only updated minutes after my last #2246 comment.
As per #2246, the beta repository is a supplemental one. Add the stable repository.
It seems that, with the changed command line, a load of ~37% drops to ~29-30%.
Your logic makes sense
Closing as invalid: the shadow server users polling, which consumes a lot of CPU.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2250