I've been tasked to look at any performance benefits
of using Subversion over CVS, and I thought this was
too cool to keep to myself.
This is not an exhaustive test, but I wanted to
compare common version control activities. We
currently have a CVS fileserver which hosts our source
files. I used cvs2svn to convert it to SVN, creating
a new SVN Repository on the same box as the CVS
repository. I've using svnserve as the process
hosting requests (it's all within the firewall), and
the machine issuing the command is on a different
machine than the repositories.
For the record, I'm comparing CVS 1.10.8 and SVN 1.2.
I've got a small fileset (512 files, 2 M) and a large
fileset (6,421 files, 128 M) which are largely
comprised of text files with the odd graphics file
thrown in.
Action CVS SVN
Check out small file set 1 m 17.32 s 26.96 s
Check out large file set 7 m 16.92 s 5m 35.01 s
Tag small file set 1m 29.30 s 0.88 s
Tag large file set 18 m 52.45 s 0.86 s
Update small file set 44.46 s 4.91 s
Update large file set 8 m 53.39 s 38.62 s
Create a branch of the small file set 1 m 27.99 s 0.80
s
Create a branch of the large file set 21 m 2.93 s 0.69
s
Send instant messages to your online friends http://au.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 10 00:43:36 2005