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

Re: Berkeley DB problem: "Could not allocate memory"

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-08 16:08:58 CET

>>> I've tried increading the "cache", as was said in a previous thread
>>> in
>>> this mailing list, by adding "set_cachesize 0 8388608 1" to
>>> db/DB_CONFIG
>>> and running "svnadmin recover". According to the users the problem
>>> only
>>> got worse.

I though that the "cannot allocate memory" problems were often fixed by
increasing not the db cachesize, but the log buffer size and
log_regionmax. Isn't that what our chats with Keith Bostic mentioned?

I'm talking about the variables

set_lg_bsize 262144
set_lg_max 1048576
set_lg_regionmax 131072

If you 'svnadmin create' a repository, look at the docs surrounding
those variables.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 8 16:49:45 2005

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.