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

thread problem OpenLDAP 2.1.8 + Solaris 8 -- slapd locks or dies

--On Friday, November 08, 2002 3:59 PM -0800 "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> wrote:

That's awful low performance.  On relatively small systems,
performance in the 1000s of queries per second range is
easily achievable.   Likely you don't have the right
indices or the indexing is ineffective due to the number
of total entries.  In the later case, you might try
increasing the IDL sizes in back-bdb/idl.h.  You might
also look at BerkeleyDB environment settings.


We have switched to Heimdal K5 instead of MIT Kerberos. That has resulted in some performance gain. Perhaps in the administrators guide, it should note that people should not use MIT K5 at this time (under the SASL section). With Heimdal, we have gone from 7 queries/second -> 25 queries/second.

However, 2 things:
1) Resetting our ACL's to just give * by * read, we were only able to get 36 queries/second max. We have not yet re-tuned the database (We are in the process of hiring a consultant for that bit), so there may be some performance issues there.

2) slapd continues to either lock up over time, completely die, or become so slow in its responses as to be useless, during load testing.

A recent lockup had slapd running, but it would not respond to any new ldap queries. A truss on the process found that it was looping in a poll (this message was being constantly repeated, many times per second):

2082:   poll(0xFE381140, 19, -1)                        = 17
2082:   poll(0xFE381140, 19, -1)                        = 17
2082:   poll(0xFE381140, 19, -1)                        = 17
2082:   poll(0xFE381140, 19, -1)                        = 17

I am continuing to work on getting better data on the cause of these lockups/crashes/slowdowns.


Quanah Gibson-Mount
Senior Systems Administrator
ITSS/TSS/Computing Systems
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html