RealVNC slowness (WinVNC)

Sam sam.fd@wanadoo.fr
Thu Jun 12 17:01:53 2003


Well,

I've also noticed this 15 seconds delay before being 
able to take the controle of the mouse.

As Ultr@VNC handles both ZRLE and Tight encoding, 
comparizons are more easy:

- It is when the connection is really slow : < 
56Kbit/s

- It happens ONLY with Tight encoding.
Mouse handling is immediate after initial screen 
loading when ZRLE encoding is used.
That's the main reason why Ultr@VNC uses ZRLE as 
default encoding in AUTO mode... (and also because 
it takes less CPU and it's faster). Don't get me 
wrong. No ideology here. I still prefer TightVNC for 
many others good reasons (options, jpeg, better 
local cursor handling... ;)

Until now, I had no time to search why Tight 
encoding causes this delay. I'm too busy with Ultra.

Both versions (RealVNC and TightVNC) have their own 
advantages and drawbacks and both are HIGH quality 
packages.


 Sam (Ultr@VNC project)