Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xpra-client of shadow has a constant ~35% CPU #2250

Closed
totaam opened this issue Apr 3, 2019 · 11 comments
Closed

xpra-client of shadow has a constant ~35% CPU #2250

totaam opened this issue Apr 3, 2019 · 11 comments
Labels

Comments

@totaam
Copy link
Collaborator

totaam commented Apr 3, 2019

Issue migrated from trac ticket # 2250

component: client | priority: major | resolution: invalid

2019-04-03 11:01:10: stdedos created the issue


Shadow-server:
2019-04-03 11:40:49,790 xpra GTK2 shadow version 2.5-[r22096](../commit/7ef6c348c85fc4b162b480215df86cbfa2dba02e) 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](../commit/9632bbcf26034732fde214891f741018f63048a5)"
2019-04-03 11:40:51,056 Python/GTK3 Microsoft Windows 10 aero client version 2.5-[r22135](../commit/9632bbcf26034732fde214891f741018f63048a5) 64-bit
Xpra-Client-Python3-x86_64_2.5-[r22135](../commit/9632bbcf26034732fde214891f741018f63048a5)\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

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 11:01:33: stdedos uploaded file xpra-ProcessHacker_2019-04-03_12-06-37.png (65.7 KiB)

xpra-ProcessHacker_2019-04-03_12-06-37.png

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 11:02:10: stdedos uploaded file display-0.log (7.3 KiB)

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 15:17:21: antoine changed owner from antoine to stdedos

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 15:17:21: antoine commented


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](../commit/7ef6c348c85fc4b162b480215df86cbfa2dba02e) 64-bit

That's older than 2.5 final, why is that?

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 15:41:59: stdedos commented


Replying to [comment:1 Antoine Martin]:

From your log I see:

Xpra GTK2 shadow server version 2.5-[r22096](../commit/7ef6c348c85fc4b162b480215df86cbfa2dba02e) 64-bit

That'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.

@totaam
Copy link
Collaborator Author

totaam commented Apr 3, 2019

2019-04-03 15:45:58: antoine commented


As per #2246, the beta repository is a supplemental one. Add the stable repository.

@totaam
Copy link
Collaborator Author

totaam commented May 17, 2019

2019-05-17 09:00:20: stdedos commented


It seems that, with the changed command line, a load of ~37% drops to ~29-30%.

Your logic makes sense

@totaam
Copy link
Collaborator Author

totaam commented May 17, 2019

2019-05-17 09:00:30: stdedos uploaded file display-%3A0.log (2.9 KiB)

@totaam
Copy link
Collaborator Author

totaam commented May 17, 2019

2019-05-17 09:04:46: antoine changed status from new to closed

@totaam
Copy link
Collaborator Author

totaam commented May 17, 2019

2019-05-17 09:04:46: antoine set resolution to invalid

@totaam
Copy link
Collaborator Author

totaam commented May 17, 2019

2019-05-17 09:04:46: antoine commented


Closing as invalid: the shadow server users polling, which consumes a lot of CPU.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant