Re: Measuring activity/problem with timeouts

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Monday, January 17, 2005 11:39 AM -0800 Rob Tanner 
<rtanner@linfield.edu> wrote:

> > On a slightly separate note, OpenLDAP 2.2.17 had memory leak & cacheleak
> > issues.  You might want to upgrade to the latest OL stable version
> > (2.2.20).  I also have two patches to OL 2.2.20, one that fixes a problem
> > with slurpd replication where changes can be lost if there is a high
> > volume of changes, and one that fixes an issue that can occur with
> > indexing using back-bdb.
>
> Based on the above, I've gone ahead and upgraded.  I've also increaed the
> cachesize from its default of 100k to 20000k.  I'll know tomorrow weather
> any of that helped.

What database backend are you using? back-ldbm? back-bdb?  If you are using 
back-bdb, make sure your DB_CONFIG file is properly tuned as well.  A very 
large entry cache may or may not help a lot, it will depend on your system 
resources.  You may also wish to set and idlcachesize as well, if using 
back-bdb.

For back-bdb, see:

<http://www.stanford.edu/services/directory/openldap/configuration/slapd-conf-replica.html>
<http://www.stanford.edu/services/directory/openldap/configuration/bdb-config-42.html>

Just to note, for Stanford's 60k accounts, I only store 20k in my entry 
cache, and that seems quite sufficient.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin