![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 05/06/18 07:14, H Zeng wrote:
On Monday, 4 June 2018 17:22:25 BST Hendrik Woltersdorf wrote:
I've seen high cpu usage in xfreerdp, when the app on the remote site made use of GPU acceleration; in my case it was firefox.
Thank you, Hendrik. That makes sense because I was doing some CAD operations that caused much screen refreshing/updating.
One option, you could try, is : /network:auto I got this recommendation from the upstream developers, but don't expect any miracles. Do you mean that my local machine was struggling to keep up with the updated screen? I tried the option but no effect.
I heard that xfreerdp transfers screen as screenshots from remote to local and displays them for local screen. Maybe the problem is that `X` takes too much resource to show the images?
Yep, generally large screen updates like this can be done with opengl which transfers most of the CPU load to the GPU (even in the case of playing video etc), whereas in this case each image is being decoded over the network via the CPU which is why it comes under significant load. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B