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

Re: Why does 'svnadmin dump' takes up so much space?

From: Andreas Stieger <andreas.stieger_at_gmx.de>
Date: Tue, 31 Aug 2010 10:40:51 +0100

On 31/08/2010 10:36, albert kong wrote:
> My repository now is totally only 70M, has 3000+ revisions, Now I want to
> dump r2647:r2871, So I use such command 'svnadmin dump E:\myrepository -r
> 2647:2871> f:\my1.dump', wait a long time, after it finishes, I check file
> f:\my1.dump, it's already 500M.
> Why does it takes up so much space(more than original repository)?


"The second useful option is |--deltas|. This option causes *svnadmin
dump* to, instead of emitting full-text representations of file contents
and property lists, emit only deltas of those items against their
previous versions. This reduces (in some cases, drastically) the size of
the dump file that *svnadmin dump* creates. There are, however,
disadvantages to using this option—deltified dump files are more
CPU-intensive to create, cannot be operated on by *svndumpfilter*, and
tend not to compress as well as their nondeltified counterparts when
using third-party tools such as *gzip* and *bzip2*."

> Question2: actually r2647:r2871 is the begining and end of a project in the
> repository, but not sequent(Sorry for my poor english, I mean like r2650
> r2651... is not revisions of this project), I just want to dump the data of
> this project, and integrate the dump to another repository, Can I achieve
> that, and How?




To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-08-31 11:41:05 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.