[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Antwort: Re: Problem using subversion on a large repository

From: <kmradke_at_rockwellcollins.com>
Date: Fri, 24 Oct 2008 10:16:14 -0500

Andreas.Otto_at_versit.de wrote on 10/24/2008 06:37:33 AM:

> Hi,
> thanks for the answer ... now my results ..
> -> yeah you are right Repository size is right now:
7270760 K -> 7G
> I try hard to solve this Problem -> now I present my experience:

> 1. this doesn't work:
> ->svnadmin dump -r $(svnlook youngest $OLD) $OLD |
> svndumpfilter exclude mytags | svnadmin load $NEW
> the reason is to delete the huge "mytags" tree created
> "svn copy ..." with dumpfilter !after! "svnadmin dump"
> was unuseable slow because before deleting you have to
> everything ~1TB (just a assuming) before you can filter

Using "svnadmin dump --deltas $REPOS_PATH > repo.dump" doesn't typically
create a dumpfile much larger than 2x the repo size on the server.
(At least in my experience on 50G+ sized repos)

Without the --deltas option, the dumpfile will contain a complete copy of
each revision, which can get quite large.

> 2. the solution was to delete the whole tags directory first
> -> svn delete ....
> and than using the command above to create the new
> repository, but i have to say:
> -> createing tags with "svn copy ...." is a design error

> nice for small projects but not useable in a big
environment !!!
> 3. I just support the "oldstyle" position that
> -> svn dump OLD | svn load NEW
> should create a repository NEW with close the same size
as OLD

It will. If OLD was a svn version before 1.4, NEW will probably even
be smaller than OLD...

Kevin R.
Received on 2008-10-24 17:16:59 CEST

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.