Hello Quanah, First I would like to thank you for your answer.
Indeed, I also think that the "cardnumber" index is somehow corrupted. His size is to small in comparison to other indexes We suppressed all existing index and Used slapindex to re-create them all. It's undergoing. I will keep you informed about the solution. Best Regards, Mathieu 2012/1/3 Quanah Gibson-Mount <[email protected]> > --On Friday, December 23, 2011 11:27 AM +0100 "External Mathieu DEDECKER > (CAMPUS)" <[email protected]**> wrote: > > Hi @All, >> >> We meet a performance problem with our OpenLDAP. >> >> We think that we face a problem with the index of the database, and we >> think that the problem can be resolve by tunning the config (but not >> sure). >> >> We would like to be sure that our configuration is correct, in order to >> confirm if we are on a wrong track or not. >> >> [Description] >> >> We have an attribute (cardNumber) which is indexed. >> >> When we request the indexed attribute (cardNumber) with an LDAP Client >> (Ldapbrowser), we have either fast or very long response time. >> >> For the long response time, the CPU of the server hits 100%. >> >> For example: >> >> Request1: cardnumber=2098001010034 (less than 1sec) >> Request2: cardnumber=2090389917486 (nearly 20 sec). >> >> By checking the hit ratio of the attribute, we can see that cache is >> correctly used (97%). >> > > It sounds like you added an index to cardnumber after there was already > data for cardnumber in your database, and didn't run slapindex for that > attribute. Alternatively, your cardnumber.bdb file is corrupted. > > --Quanah > > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration >
