On Saturday 24 January 2004 17:37, �var Arnfj�r� Bjarmason wrote: > Attached is a recent test i did on subversion regarding exactly this, the > the size of the repository I came to the same conclusion as you (the db is > big) in this case 161MB for a raw import of portage versus CVS's 70MB. > > However this is due to the Berkley DB leaving behind a lot of log files > which in all normal use are usless and can be safely deleted. (these are > not the commit-diffs) > > After i deleted these unused log-files the previously 161MB subversion > repository of portage took 49MB or more then threefold reduction in size > without any loss of version info or files. > More info can be found in the subversion manual at -> > project_faq.html#bdblogs which deals specifically with why the repository > gets so big. > > The subversion admin can regularly remove these logfiles from the > repository through the use of a cron job in older versions or just leave > the default log-pruning on in versions >=0.35. > > So not only was the statement about subversions database being bigger > wrong, its quite the opposite; its smaller. > > > That would make > > subversion dumps quite painfull. Further subversion is not really good > > in such big repositories > > Elaborate, why does it not handle the big ones well? >
I have not tested it in a long while. What happened was that IF I was able to actually check in the whole tree into the repository checking out would both take too much time and fail somewhere in the meantime on some lock or out-of-memory error. It can very well be that this has been fixed by now, but I didn't check. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgp00000.pgp
Description: signature
