On 2/20/11 11:27 AM, Martin Koegler wrote: > Adding SSH Tunnling to the comparison would be interesting (the CPU > time of ssh must be added to the server/client time, as the SSH > process does the crypto operations on behalf of TigerVNC).
To be clear, the CPU time in my measurements was the system-wide CPU time, not the CPU time of just the TigerVNC process. I'll repeat the measurements for SSH. > Hasn't the pentium 4 suffered from log pipelines (high clock > frequency, but fewer operation per clock cycle)? Yes, but the Intel processor in my Mac suffers a similar type of hit-- not as bad as the P4, but still not nearly as good as the AMD. Need to get hard numbers there as well. > If somebody wants to improve the overall performance of Xvnc, > ComparingUpdateTracker::compareRect could be of interest. It's on my radar for sure. One of the things I had to do for TurboVNC was to change up the Tight encoder/decoder so that they can operate on the raw virtual framebuffer rather than having to translate it into RGB. I need to do the same for TigerVNC. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
