ti...@piments.com wrote: > > VNC context: > > > > All tiger vnc software is run on the remote kubuntu box via ssh from > > local linux system. > > > > r...@local# ssh -C -X -L 5900:localhost:5900 remote.dyndns.info > > r...@remote:~# vncviewer localhost:0 > > > I'm wondering whether running this way means the vnc compression is > irrelevant to the network section since it is happening between two > processes on the same machine.
That isn't really the way it works. The VNC compression is still occurring between the local and remote machines. It's just that the compressed VNC stream is being re-processed (encrypted and re-compressed) by the SSh tunnel. However, I'm not sure if TigerVNC behaves this way, but I know that other VNC implementations will detect if a connection is to localhost and automatically default to using Raw compression (that is, no compression.) That seems to be the way your configuration is behaving, based on the fact that SSh compression seems to speed things up (which it shouldn't do if your image stream was actually being compressed by VNC.) One thing we never established is whether JPEG compression is active for your VNC sessions. Whenever you drop the JPEG quality down to, say, 2 or 3, do you see noticeable JPEG compression artifacts? If not, then JPEG is not being used, and that's why it's running so slow. > It does run with expected performance running viewer on client machine > via an insecure port > but that is unacceptable. > > Is there a better way? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
