CVS Performance

I have huge projects in the CVS repository and am looking for ways to improve its performance. Did CVS Compression Help? What about encryption, does it degrade speed?

Thanks!

+5
source share
3 answers

After repeated use, CVS will become slower.

  • When you upload the entire project, the server will need to create each directory (even if you deleted it) - cleaning the directories after checking hides this from you).
  • When you exit, each file is opened and checked, it can be very slow if you have hundreds / thousands of files.
  • , HEAD , .

, ( ) -z . , -z6 , / .

-z GZIPLEVEL

. GZIPLEVEL 1 9. 1 - ( , ); 9 - ( , , ). 9 . 3 5, .

-z .

+9

IO. ( , CPU 100%). (RAID 10 / RPM-), , . , , , , , , DSL- .

+3

cvs afaik, ssh ssh ( , ). . edit: cvs -z ( ssh -C)

Encryption is not something useful to improve performance. Using ssh will also do encryption, but this is not for performance, but for security.

Wherever the repository is located, disk access for the repository and temporary files will affect performance. This is combined with memory. When checking, cvs will build what it sends to the client (as temporary files). This caused a lot of malfunctions and, in some cases, the use of memory (esp when working with large binary files).

+2
source

All Articles