On Fri, Aug 17, 2001 at 09:01:35PM -0500, subversion-dev@thewrittenword.com wrote:
> On Fri, Aug 17, 2001 at 12:42:30PM -0700, Greg Stein wrote:
> > On Fri, Aug 17, 2001 at 05:07:54AM -0500, kfogel@collab.net wrote:
> > >...
> > > copy bugginess, but repository maintenance issues are another story.
> > > We need to get that stuff fixed before self-hosting.
> >
> > The maintenance that Karl is referring to here is w.r.t the log files. The
> > database grows pretty large due to the log files. There is some stuff in the
> > DB docs about how to archive the db, and more specifically: how to detect
> > which log files are no longer in use (and can be rm'd). We need to get some
> > basic maintenance instructions/procedures figured out and in place.
>
> FYI, for our Berkeley DB-based application, just before we close the
> database, we issue txn_checkpoint() and then remove any log files
> returned by log_archive(DB_ARCH_ABS). For lots of commits, the log
> files will grow and grow and grow but things settle down with normal
> use.
We already do the txn_checkpoint, but not the log_archive.
I'm not sure exactly what strategy we're going to want to use. Note that a
commit of a single file will probably open/close the DB environment a half
dozen times. It is probably about 2 or 3 times per file changed after that.
So... while a txn_checkpoint() would be good, examining log files or
whatever could be overboard. Of course, the real answer is to instrument the
stuff and see what we get.
For the most part, I'm considering the policies to use for the DB, in terms
of what DB utilities to run when / how often.
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
Received on Sat Oct 21 14:36:36 2006