Re: Mass-commit results...

On Wed, Aug 29, 2001 at 11:23:55PM +0200, Branko �ibej wrote:
> kfogel@collab.net wrote:
> >Just so people know, "archival" here means simply
> >
> > $ cd /path/to/repository/db
> > $ /usr/local/BerkeleyDB.3.3/bin/db_archive | xargs rm
> >
> >db_archive, when invoked like that, just tells you what log files are
> >no longer being used.
>
> Would it make sense to have a post-close hook that could do this
> automatically?

Nah. I'd think this would be something to run in a cron job. For busy
repositories, maybe once an hour. Most repositories could go once a day or
once a week.

It is simply when we slam a repository with 1000 commits, it does tend to
grow very fast. Most repositories don't see that kind of activity. As
measured by the number of messages in the archive cvs@subversion.tigris.org,
we've seen 4255 commits to the repository in its 14 months of operation.
That is about 70 commits per *week*. So... your mileage will vary, but the
archival certainly doesn't need to run on every commit.

For the upcoming SVN repository, we'll probably go once a day, with a report
mailed to the svn administrator.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org