I have a local X-Server with x11-drivers/xf86-video-intel-2.16.0 and x11-drivers/xf86-input-evdev-2.6.0, configured to use the xorgmodule from tigervnc. When I remotely connect to the X-Server, the CPU usage of the X-Server process (X) goes to nearly 100% and I get a very poor performance when working remotely. When closing the remote connection and working locally the cpu usage returns to normal values. Reproducible: Always Steps to Reproduce: 1. start a local X-session 2. tigervnc to this Display 3. watch cpu load Actual Results: CPU load high, bad performance Expected Results: normal CPU usage, nearly the same performance as when working locally (at least when connected directly within the same subnet)
maybe this is already addressed in tigervnc-1.1, but unfortunately there's no ebuild for it yet :-(
There it is now(In reply to comment #1) > maybe this is already addressed in tigervnc-1.1, but unfortunately there's no > ebuild for it yet :-( There it is
(In reply to comment #2) > There it is now(In reply to comment #1) > > maybe this is already addressed in tigervnc-1.1, but unfortunately there's no > > ebuild for it yet :-( > > There it is ... your're right, but unfortunately I still do have high CPU Usage :-( But I do see some improvement, CPU usage is at about 50% max. Better than before, but still not optimal. Gerhard
(In reply to comment #3) > (In reply to comment #2) > > There it is now(In reply to comment #1) > > > maybe this is already addressed in tigervnc-1.1, but unfortunately there's no > > > ebuild for it yet :-( > > > > There it is > > ... your're right, but unfortunately I still do have high CPU Usage :-( But I > do see some improvement, CPU usage is at about 50% max. Better than before, but > still not optimal. > > Gerhard I did some testing and discovered, that the load decrease is due to sna useflag introduced in recent versions of xf86-video-intel and _not_ due to some changes in tigervnc.
@x11?
I don't know why this happens. Perhaps some profiling and reporting the results upstream would be good.
Reopen if still happens with recent versions