RE: Re: SVN database is a lot bigger than PVCS database
From: Seak, T. F. <lapsap7+svn_at_gmail.com>
Date: Wed, 22 Jul 2009 09:35:27 -0700 (PDT)
> If you are using svn 1.6.3 there really is nothing you can do other than dumping your repository and filtering out some older content.
We're using VisualSVN 1.7.1
We've been using it for the last 6 months. So we can't "dump" it.
I knew nothing of the migration as that's not my project (not my job). But now I've heard users telling that SVN is very slow (in LAN) that I think I need to find out the cause. IMO, one of the possible causes is the big database size.
> If you used the Polarion importer than there is a setting in the properties files to have it use svn copy to make tags and branches. Check to see if you used it. If you didn't you may want to consider redoing your migration and replaying the changes from when you started using SVN into it.
Is it possible to "replay" all the changes automatically? We've been using it for more than 6 months.
> That all said, disk space is pretty cheap these days.
Yes, I know, but there're a few reasons why I need to look into this matter. 1) Performance as I stated earlier. 2) Backup: the bigger the database, the longer it takes to backup. BTW, we have no idea if there's any official way of backing up the DB. We're just thinking of copying everything to another server through network. Estimated time to transfer 27GB is about an hour. And we're supposed to do so everyday. 3) I'm going to move SVN into a virtual machine. Then again, it's nicer to have a smaller database as big virtual disk would mean lesser performance.
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.