From: H.S. <hs....@gm...> - 2008-02-15 05:10:54
|
Hello, I am looking for speeding up the interaction with a Windows desktop running tightvnc server and viewing it on a Linux machine over a long distance DSL connection (the connection is not very fast though, 256/64 kbps). Mainly, how should the VNC server on the Windows XP machine be configured to get best performance. I already use a command like the following on the Linux client: $> xtightvncviewer -compresslevel 9 -encoding "copyrect hextile tight" localhost:1 This connection is through an SSH tunnel, hence the localhost above. thanks, Sam. |
From: Bob M. <rvm@CBORD.com> - 2008-02-15 13:28:26
|
The trick is to reduce the amount of image data that has to be transferred initially and with each update. Make sure "Remove desktop wallpaper" is turned on so the background image does not have to be transferred or refreshed. Make each window as small as is practical. Minimize windows you are not using but that may change while you are focused elsewhere. Bob McConnell -----Original Message----- From: vnc...@li... [mailto:vnc...@li...] On Behalf Of H.S. Sent: Friday, February 15, 2008 12:11 AM To: vnc...@li... Subject: vnc over long distance and relatively slow DSL connection Hello, I am looking for speeding up the interaction with a Windows desktop running tightvnc server and viewing it on a Linux machine over a long distance DSL connection (the connection is not very fast though, 256/64 kbps). Mainly, how should the VNC server on the Windows XP machine be configured to get best performance. I already use a command like the following on the Linux client: $> xtightvncviewer -compresslevel 9 -encoding "copyrect hextile tight" localhost:1 This connection is through an SSH tunnel, hence the localhost above. thanks, Sam. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ___________________________________________________________ TightVNC mailing list, VNC...@li... To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |
From: H.S. <hs....@gm...> - 2008-02-15 17:23:28
|
Bob McConnell wrote: > The trick is to reduce the amount of image data that has to be > transferred initially and with each update. > > Make sure "Remove desktop wallpaper" is turned on so the background > image does not have to be transferred or refreshed. Already done. > Make each window as small as is practical. hmm ... didn't have that in mind. > > Minimize windows you are not using but that may change while you are > focused elsewhere. Yup, that is being done as well. thanks. |
From: James W. <jn...@re...> - 2008-02-15 15:44:59
|
Hi Sam, The first thing to check is the end-to-end latency, e.g. by pinging the server computer from the viewer. If the network latency is high then you may actually be better off disabling as much compression as you can, since that further increases the latency of update delivery. Cheers, -- Wez @ RealVNC Ltd > -----Original Message----- > From: vnc...@li... > [mailto:vnc...@li...] On > Behalf Of H.S. > Sent: 15 February 2008 05:11 > To: vnc...@li... > Subject: vnc over long distance and relatively slow DSL connection > > Hello, > > I am looking for speeding up the interaction with a Windows > desktop running tightvnc server and viewing it on a Linux > machine over a long distance DSL connection (the connection > is not very fast though, 256/64 kbps). Mainly, how should the > VNC server on the Windows XP machine be configured to get > best performance. > > I already use a command like the following on the Linux client: > $> xtightvncviewer -compresslevel 9 -encoding "copyrect > hextile tight" > localhost:1 > > This connection is through an SSH tunnel, hence the localhost above. > > thanks, > Sam. > > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft Defy all > challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ___________________________________________________________ > TightVNC mailing list, VNC...@li... > To change your subscription or to UNSUBSCRIBE, please visit > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list > |
From: H.S. <hs....@gm...> - 2008-02-15 17:25:09
|
James Weatherall wrote: > Hi Sam, > > The first thing to check is the end-to-end latency, e.g. by pinging the > server computer from the viewer. If the network latency is high then you > may actually be better off disabling as much compression as you can, since > that further increases the latency of update delivery. Interesting. Currently I am using maximum compression (-compressleve 9). I will try using lesser next time and see how it goes. BTW, when the VNC server is on Windows XP, how do I reduce the color bits on a new client session? thanks. > Cheers, > > -- > Wez @ RealVNC Ltd > > >> -----Original Message----- >> From: vnc...@li... >> [mailto:vnc...@li...] On >> Behalf Of H.S. >> Sent: 15 February 2008 05:11 >> To: vnc...@li... >> Subject: vnc over long distance and relatively slow DSL connection >> >> Hello, >> >> I am looking for speeding up the interaction with a Windows >> desktop running tightvnc server and viewing it on a Linux >> machine over a long distance DSL connection (the connection >> is not very fast though, 256/64 kbps). Mainly, how should the >> VNC server on the Windows XP machine be configured to get >> best performance. >> >> I already use a command like the following on the Linux client: >> $> xtightvncviewer -compresslevel 9 -encoding "copyrect >> hextile tight" >> localhost:1 >> >> This connection is through an SSH tunnel, hence the localhost above. >> >> thanks, >> Sam. >> >> >> -------------------------------------------------------------- >> ----------- >> This SF.net email is sponsored by: Microsoft Defy all >> challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> ___________________________________________________________ >> TightVNC mailing list, VNC...@li... >> To change your subscription or to UNSUBSCRIBE, please visit >> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ___________________________________________________________ > TightVNC mailing list, VNC...@li... > To change your subscription or to UNSUBSCRIBE, please visit > https://lists.sourceforge.net/lists/listinfo/vnc-tight-list > |
From: Ron J. <rj...@ya...> - 2008-02-15 17:49:40
|
On Friday 15 February 2008 00:10, H.S. wrote: > This connection is through an SSH tunnel, hence the localhost above. Are you compressing the ssh tunnel (-C) ? |
From: Constantin K. <co...@ti...> - 2008-02-21 19:19:10
|
Hello Sam, >>>>> H.S. wrote: > I already use a command like the following on the Linux client: > $> xtightvncviewer -compresslevel 9 -encoding "copyrect hextile tight" > localhost:1 > > This connection is through an SSH tunnel, hence the localhost above. Just for your information: the command line above causes the server always use the Hextile encoding (because it is listed before Tight). That also means the -compresslevel option does not have any effect, because it affects only the Tight encoder. -- With Best Wishes, Constantin |