Re: BDB log files growing for read-only operations

Young Hyun <youngh@caida.org> writes:
> Why do the Berkeley DB log files grow for conceptually read-only
> operations like svnlook, 'svn list', and 'svn cat'? I am especially
> surprised about svnlook.
>
> Specifically, try this:
>
> perl -e 'my $x = 100; while ($x--) { print $x, "\n"; \
> `svnlook youngest /path/to/repos`; }'
>
> and look at the size of your log files before and after.

Because Berkeley's transaction management system has its own overhead
in the db, which requires the log files.

> I'm managing a slowly changing repository that will get a moderate amount
> (~400-800/day) of read-only requests, and it seems wasteful for the logs
> to grow when nothing is actually changing. It becomes wasteful if I
> choose to slavishly back up the logs (which I probably won't).

Btw, see contrib/server-side/backup-recipe.sh in the Subversion tree
for an example of a backup system which removes logfiles when they are
no longer needed.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 11 18:01:18 2004