Why is CVS running so slowly?
This can happen for any number of reasons, but usually it’s because you are making too many demands on your server resources. Increasing memory on the repository server and removing other programs which take up CPU time can help. You can get up to a tenfold speed increase by using a temporary file system (/tmp) on a RAM disk (in memory). When a large number of concurrent users are accessing a CVS server simulateously, that can cause a large number of CVS processes to be forked. Each CVS process can consume memory equal to ~ 2-3X the largest file size the CVS command is trying to process. This can cause issues like SWAP space becoming too low or too much CPU load being placed on the system. You can offload a large CVS repository by creating multiple active replicas using commercial tool like WANdisco CVS Replicator. This tool can effectively allow you to scale horizontally by clustering multiple machines to act as one virtual repository. Thus you can share CVS traffic across multiple ma
