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

Re: Repository Size Growing VERY Quickly

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-07-21 01:35:46 CEST

  ----- Original Message -----
  From: J Kramer
  To: Daniel Berlin
  Cc: users@subversion.tigris.org
  Sent: Thursday, July 20, 2006 7:02 PM
  Subject: Re: Repository Size Growing VERY Quickly

  On 7/20/06, Daniel Berlin <dberlin@dberlin.org> wrote:
    J Kramer wrote:
> All,
> At my workplace we use SVN to manage our software development. We
> commit rather frequently as that seems good policy, but the size of the
> SVN repository (on the server) is growing quite rapidly--too rapidly for
> us.

    You need to quantify these terms with numbers.

  In the past week the repository has grown from about 500 MB to 1.7 GB. We should be able to take care of some of that by unversioning some things that are currently versioned, but most of our binary files have to be versioned.

    It depends on the size of the binary files, and how they are changing.
    If we are talking gigabyte files, you'll probably want to up the window
    size a bunch (at the cost of memory and time usage) to get better delta
    This requires modifying one of the include files.

  Could you explain more about that? I'm not familiar with that parameter.

  Also, for files that currently exist in the repository that aren't needed, how can we expunge them from the repository? If we simply delete them, then there will be no new versions, but SVN will continue to keep the old versions.

The only graceful way to expunge old files currently is to use svnadmin dump, svndumpfilter, and svnadmin load in combination to skip the undesired files. Like many other systems, Subversion is designed to *NOT* throw away data. This can occasionally be burdensome, for example in your current case.
Received on Fri Jul 21 01:37:01 2006

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.