> One place I worked for had CVS performance trouble. They were
> using it over NFS, client-server, and a number of other ways.
> After cleaning things up, going completely client-server, and
> using local disk for both the repo, and the client-side, they
> saw at *least* a 10-fold improvement. (Ok, there was a server
> upgrade in there as well...) My "rule" with CVS has always been:
>
> Use client-server, use local disk.
By the way, at the site that I am currently working (UWiscCS),
just about all diskspace is AFS. Local disk is not backed up.
Only AFS disks are backed up. It would be rather stupid to
put a CVS repository on a local disk in such a situation.
Now, one could run CVS server with a repository on an AFS
filesystem that was never accessed remotely.
