> 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.
Unfortunately, I have never yet worked in a place where I was allowed
to set up my own CVS server. Or, if I had control over my own machine,
where my CVS server could network across the various intra-company
gateways to all the places where I and others needed to access it.
But, in that same company (which also happens to be the one Michael
is working at) AFS went everywhere.
Going client-server only will make CVS impossible to use for small,
ad-hoc, users who are not officially supported by their companies.
E.g. I use RCS for all of my personal files, .cshrc, etc. I was thinking
of going to CVS, but if CVS is client server only, I will not be able to.
