[Date Prev][Date Next]
Re: BDB-openldap performance
--On Tuesday, May 31, 2005 1:25 PM +0000 Manel Euro <firstname.lastname@example.org>
I am having performance problems on my openldap-2.2.26 and Berkeley
I have installed this combo on a PIII 1.0Ghz with 512 Mb and an IDE drive.
Every client has nscd configured and running.
Whenever a client does:
cd ~username (and then tab) I get the following error:
Ex: my username is tsoli;when I do cd ~tso(and TAB) it circles the globe
two times :) and gives me tsoli.
Here is the error:
/usr/local/openldap-2.2.26/libexec/slapd -d 4
SRCH "ou=People,dc=ex,dc=com" 2 3 0 30 0
attrs: cn uid uidnumber gidnumber gecos description homeDirectory
send_ldap_result: err=0 matched="" text=""
Here is the bdb section in slapd.conf
# Indices to maintain
index objectClass eq
index cn,sn eq,pres,sub
# Indexes para optimizar o acesso para as funcoes getpwuid(), getpwnam()
# e getgrgid()
index uid eq,sub
index uidNumber,loginShell eq
index gidNumber eq
index uniqueMember pres
index memberUid eq,pres,sub
cachesize applies to the number of entries in your database. Do you really
have 1,500,000 entries in your DB?
The dbcachesize parameter does not apply to back-bdb if that is the
database you are using. It only applies to back-ldbm.
# logfile 100MB, a BDB .
# set the in-memory log buffer size
# temporary while we're slapadding the database
# set the cachesize to 0GB + X bytes, split into N pieces of memory.
set_cachesize 0 150000 1
I got 150Kb when performing the calculations recommended in the OpenLdap
I would guess that 150KB is way too small. Try at least a few megabytes.
I will note that it is suggested to use OpenLDAP with BDB 4.2.52+patches,
and not with BDB 4.3.x. The problem you are seeing itself seems to be a
problem with nscd (why is it searching for uid=public?).
Principal Software Developer
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html