Tony, I have noted a considerably changed (for the worse) performance in WinCvs after I installed the latest versions of both WinCvs and CVSNT. Don't know where the problem is located though. But here is a list of my changes: 1. Installed the latest version of WinCvs 2. Installed the very latest version of CVSNT (self compiled from sources) 3. Copied the cvs.exe and protocol dlls from CVSNT to WinCvs
Two tested connections: A) ntserver to a W2000 box accessed via a 700 kbps VPN over Internet B) pserver to the CVSNT repository Whenever I do certain operations from WinCvs on A) it takes almost forever: - Graph a file I tried this again yesterday and after waiting for about 5 minutes after WinCvs showed the message "checking out revision 1.23" or similar I clicked the red stop button. - Diff a file (I have set up ExamDiff as my diff utility) Same basic behaviour as for Graph, many minutes of waiting time. Had to stop. Then I copied away the local file and updated to the revision I wanted to diff. The update took only a few seconds (5-10), then I could use ExamDiff locally on the two files to find the differences. Not a good solution but much quicker. - Update a module Takes longer than before, especially on big files like binary exe when the output window hangs for a long time. Operatiosn on B) (your server over the Internet, so it should be basically the same speed): - Graph a file Takes just the expected amount of time, about 10 seconds or so - Diff a file Same here, ExamDiff shows up in next to no time in comparison - Update a module This is faster too, but since there are no large binary files in your module I can't compare the performance of the update. All of the above tests were using the same WinCvs client. I guess this is somewhere in WinCvs then? /Bo -----Original Message----- From: Tony Hoyle [mailto:[EMAIL PROTECTED]] Sent: den 6 mars 2002 20:10 To: [EMAIL PROTECTED] Subject: Re: [cvsgui] Wincvs 1.3.7.1 beta 7 is EXTREMELY SLOW! Tony Hoyle wrote: > I've noticed a slowdown with the recent WinCVS too... executing from > the command line runs at normal speed so there's something interacting > badly in the GUI. If I get the chance I'll try some older versions to > see if I can pin it down. > Ahh false alarm... I still had debugging enabled in the cvs.exe that WinCVS was using. It's back to normal speed now. Tony _______________________________________________ Cvsnt mailing list [EMAIL PROTECTED] http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
