[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: cvs status sends every file to server. slow performance

From: Arthur Barrett
Subject: RE: cvs status sends every file to server. slow performance
Date: Tue, 25 Jul 2006 04:22:57 +1000


> Hi, when using cvs status on a 
> project I receive the following
> O:\CobEntw\X\A>cvs -t status

Are you using CVS or CVSNT (which is more common on Windows and is
free/GPL and still runs on Linux too)?

If you are using CVSNT please upgrade to a newer version and post your
Q's to the CVSNT list.

As others have pointed out this problem occurs when the file date/time
has changed.  Some improvements have been made in 2.5.03 and we have
major changes (to improve this) planned in 2.5.04 or 2.6 (depending on
various factors).

> -> main loop with CVSROOT=:pserver:address@hidden:2402/cvsmat/cvsroot

If you are using CVSNT, then using Port 2402 is a bad idea since that is
the standard port for the lock server...

> out on a unix machine, transferred to dos 
> and then copied to that directory.

Consider checking out directly on DOS/Windows.

On a directory that is not modified. I receive the following output
that is ok.

>    Sticky Options:      -kb

Binary files can be particularly poor performance with the status

> Can somebody explain me the reason for the 
> "file sending". 

To determine if the file content has changed.  If you don't need that
information then "cvs log" provides much of the same info without the
need to send the file to the server.  

Using some network compression "cvs -z9 status" may improve performance
if you have plenty of free CPU on client and server.

> But our Users want an automatic update
> on this dir uppon each commit. 

Then look into either running the CVS server on Windows so this
directory can be directly updated or or make it a SAMBA share off Linux
(shudder).  As someone else pointed out "automatic updates" can be
achieved with a postcommit trigger or in CVSNT with the "shadow"


reply via email to

[Prev in Thread] Current Thread [Next in Thread]