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

Re: Crash after large deltas

From: Branko Čibej <brane_at_xbc.nu>
Date: 2003-04-10 10:52:10 CEST

John Goerzen wrote:

>Ben Collins-Sussman <sussman@collab.net> writes:
>>>I have tried bumping up the log sizes in DB_CONFIG, but it seems to
>>>have not helped at all. I am using 0.20.1.
>>It's not the log sizes that matter here, I think it's the maximum
>>number of locks. Try changing that instead.
>That does appear to have fixed it.
>I guess I have two questions now:
>1) Are the current defaults reasonable?

That depends on what a reasonable limit for the size of a checkin is, of
course. And that limit most likely depends on your environment.

I think we can solve some of the problem by being more careful about the
size of the transactions we create; ideally, the numer of locks used
should be constant regardless of the size of the commit. In the
meantime, it would be great if somebody could take the time and actually
document what the lock limits should be depending on commit size, so
that people could set their DB_CONFIG settings to suit their expected usage

>2) Could the error message be made more helpful? For instance,
> "Couldn't acquire a lock; see db/DB_CONFIG" rather than "Couldn't
> allocate memory"

That error messag comes from BDB, not from Subversion. I don't think
there's any way we can safely convert it.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 10 10:52:55 2003

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.