> 2. Repository size seems to be too big. 40Mb of RCS data resulted in 1.8Gb of
> SVN data.
Maybe it helps to write your own conversion script.
We had an 200 MB CVS repository; since we were not interested
into keeping the exact history, we wrote an
conversion script (calling the svn import utility script)
taking over CVS tags only. The script was a simple loop
doing a checkout + import for each CVS tag.
The resulting svn db was much smaller of the origiginal
CVS repository ((I don't remember numbers; hard to say
what the size would have been after a full conversion).
There are also other indications that the subversion
repository storage is very efficient and compact:
Our daily backup (uncompressed) svn dump file is much larger
than the berkeley database itself (after removing unused logs).
Note that dump uses file diff's and therefore does only
contain changes (at least for text files).
In numbers: Currently the svn dump is 540 MB,
the svn repository size is 224 MB.
Since CVS/RCS uses a similar mechanism than the dump file format
(diff's for text file changes), I suppose that also a CVS repository
whould need about 540 MB today.
In other words, at least in our case, the svn repository size
is about less than half the size as a cvs repository probably
would need. I think this is excellent!
My conclusion is that in your case it MUST be cvs2svn problem.
Cheers,
Folker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 21 12:08:15 2004