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

Re: svn disk usage

From: Ryan Schmidt <subversion-2008b_at_ryandesign.com>
Date: Fri, 13 Jun 2008 19:33:17 -0500

On Jun 13, 2008, at 13:13, Enrico Weigelt wrote:

> Andy Levy wrote:
>> You can only switch via a dump/load cycle (make sure when you run
>> svnadmin create for the new one you specify --fs-type=bdb).
>> http://subversion.tigris.org/faq.html#dumpload
> Okay, my repository is "just" about 120MB big yet, so I'll
> have a try within next days.
> BTW: what about compression ?

What about it? :) Data is compressed in the repository, regardless of
whether you use FSFS or BDB as the backend. Newer versions of
Subversion may compress better than older versions, so if your
repository and many of its revisions were committed with an older
version of Subversion running on the server, dumping and loading the
repository may reduce the space it takes. Switching from FSFS to BDB
could also alter how much space the repository takes, though I don't
know which would be bigger.

> BTW#2: is there any way of saving space in the working copy,
> eg. by kicking off seldomly used files in the back-copy ?
> These files could be fetched on-demand (eg. on svn diff, etc).


There are open requests to allow working copies with a compressed
text-base or with no text-base at all but no work has been done on
this that I'm aware of.



> The point is: I normally check out the whole tree, including
> all tags (for convenience), but almost never change eg. tags.

You almost certainly should check out only the trunk, not the entire
project structure. When you want to look at a tag, "svn switch" your
trunk working copy to the tag, then when you're done switch it back.
Or, keep a couple working copies around. I routinely keep a working
copy of trunk and a working copy of the active branch of whatever
project I'm working on. But don't keep the entire tags folder or the
entire branches folder. That's just going to waste your disk space
and network bandwidth and your server's resources.

> A really cool thing would be having an svn filesystem, which
> only presents what you're interested in (maybe the revisions
> could also appear as subdirs, like in fossil) and really does
> everything on-demand. It probably even would not need to have
> double-copies of each file, since it directly sees the change
> from the user.

Can't help you with that.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-14 02:34:43 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.