Re: Size of hotbackup.py files versus svnadmin dump files

Edmund Lian <elian@inbrief.net> writes:
> I just noticed that a dump of an entire repository is much smaller
> than the sum of files that hotbackup.py creates. In my case, 129Mb for
> the dump file versus 429Mb for hotbackup.py
>
> I presume the difference arises from the Berkeley DB files being quite
> sparse. Is there anything that one can do to pack them down a bit
> better for a hotbackup?
>
> Also, given that a full dump contains all all the information needed
> to recreate a repository, why doesn't the hotbackup script simply do a
> dump instead?

The dumper didn't exist when we wrote hotbackup.py. I don't know how
much more expensive it would be, in terms of execution time, to do a
dump than to just copy the files.

> This would save an enormous amount of space. E.g., a tarred/gzipped
> dump of my repository is just 28Mb versus 429Mb from hotbackup.py!!!

Well, why aren't you gzipping the hotbackup results too, if you want
to do that comparison? :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 16 21:03:18 2003