BDB log files growing for read-only operations

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.

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).

I'm running Subversion 1.0.0 with Berkeley DB 4.1.25. (Yes, these are not
the latest, but I have to use them for now.)

 --Young

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