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

Re: Subversion's use of Berkeley DB [#11511]

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-12-08 23:20:32 CET

--On Wednesday, December 8, 2004 3:21 PM -0500 Keith Bostic
<bostic@abyssinian.sleepycat.com> wrote:

> The appropriate size will depend on the database environment:
> how big are your databases, what are the data access patterns,
> what does the data look like. There are many different things
> to consider when looking at cache tuning.
> Regardless, 256KB is too small for any server application. If
> you make it even 1MB, things will likely be happier.

Okay, I just upped svn.apache.org's cache size to 256MB - we'll see how this
fares via db_stat and tweak accordingly. (The total size of our BDB
repository is ~5GB and constantly growing as we convert more projects.)

>> Can we change the cache size by just tweaking DB_CONFIG and restarting the
>> processes? Or, do we need to rebuild the database? (The docs I can find
>> aren't very helpful on this.)
> You can change the cache size by tweaking DB_CONFIG and
> restarting the processes.

After modifying DB_CONFIG, I also had to run 'svnadmin recover' to apply the
change - since I think the environment changed. I'm not sure if this is a
quirk with BDB or Subversion.

Thanks again! -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 8 23:21:56 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.