Re: svn disk usage

* Ryan Schmidt <subversion-2008b_at_ryandesign.com> wrote:

> >BTW: what about compression ?
>
> What about it? :) Data is compressed in the repository,
> regardless of whether you use FSFS or BDB as the backend.

Cool :) I wasn't aware of this.
But it doesn't look like it's compressing everything, right ?

> >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).
>
> No.

Would it be hard to implement ?

IMHO, we just need some automatic fetch when an text-base file
is needed, but missing/broken. Once this is running fine, one
could manually remove some of these files and svn will re-fetch
them on-demand. More automatic machanisms (eg. via properties)
can later build on that.

Is there currently any way for restoring specific broken text-base
files manually ?

> 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.
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=908
> http://subversion.tigris.org/issues/show_bug.cgi?id=525

hmm, compressed text-base could be a bit more tricky, IMHO,
since we'll need the logic for reading compressed files at
many places, right ?

(or just use an compressed filesystem ;-P)

BTW: one of these bugs mentions scord-fs - seems to be a fine
thing, I'll have a look at it.

> >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.

hmm, looks a bit unconvenient to me, especially when tagging.
(for now I just svn copy locally, do some things and commit -
with your approach I'll have to type in the whole repo urls :()

> 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.

hmm, the whole issue would be solved, if we had some svn-fs
which does everything on-demand (eg. only checks out local
copies when really needed). that's already in my pipeline ;-)

cu

-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org