On 11/29/11 3:34 AM, Pierre Ossman wrote: >> In the >> next-gen version of TurboVNC, manually enabling the Continuous Updates >> extension (which causes the TurboVNC server to send updates immediately >> to the client) produces significantly better throughput on this type of >> connection, but none of the TigerVNC enhancements seem to have improved >> its throughput. > > We've been focusing on responsiveness, but that should be correlated > with throughput. Example tests have been typing, dragging things around > and playing movies. > > Note that maximum throughput has explicitly not been the goal. Doing so > would have ruined latency as that fills up buffers. The goal of the > algorithm is to maximize throughput without sacrificing latency. In > practice it can of course never be perfect, but the numbers I've seen > during my tests shows that it tends to be pretty damn close. > > Further improvements can probably be made, but we're at a point where > we deem it good enough for now and are looking to put the stuff in the > hands of users first.
It would really be nice to quantify it somehow, because it doesn't seem to be any better in terms of responsiveness, either. I'm testing up in the range of 100-200 ms ping time, or rather, 50-100 ms added on both ends. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
