[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: alock File Keeps LDAP (slapd) from Starting Up

On Thu, May 25, 2006 at 06:24:55PM -0700, Quanah Gibson-Mount wrote:

>>No, it didn't fix the speed problem.  When using the ldbm backend, the
>>machine sits at load around 0.1 and 2% or 3% cpu usage.  I switch to bdb
>>backend and my load jumps to 14 or so, searches take seconds to complete
>>(of course slows down as the load gets higher).  At that point, the
>>acceptance of new incoming connects gets degraded enough that it drops
>>out of the load balancer until OpenLDAP catches up on things.  In short,
>>I wasn't able to get it to work.  I had to go back to ldbm.  I'll keep
>>hacking away at it.
>Well, since you are using a version of BDB that is recommended you not use, 
>all bets are off.  On my AMD boxes, I get some 13,000 searches/second using 
>BDB as the backend (bdb 4.2.52+patches) on a 1 million entry database.

I have db-4.2.52 installed with openldap-2.2.28, sorry I didn't make
that more clear.  I rolled the 2.3.* version back to 2.2.28 with

>As for your conf file, I don't see any idlcachesize setting.

I will investigate this one and figure out what to put there.  I'll dig
through the openldap faqomatic.

>As for DB_CONFIG, a general rule to start with is:
>Cache size should be size of id2entry.bdb + 10%, which in your case means 
>your DB_CONFIG file is not set up correctly for the cachesize.
I'm looking for docs on it.  Nothing is installed, so I'll unzip the
tarball and see if I can find it in there.  

>52428800 (your cache size setting) vs 64372736 (size of your id2entry.bdb 

If increasing that makes a difference, I'll be quite happy.  I'll try it
again this afternoon.

Thanks for the notes.
Regards...		Todd
when you shoot yourself in the foot, just because you are so neurally
broken that the signal takes years to register in your brain, it does
not mean that your foot does not have a hole in it.      --Randy Bush
Linux kernel 2.6.12-18mdksmp   2 users,  load average: 1.01, 0.61, 0.51