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

RE: Problems with openldap-2.1.22 slowing down over time.

On Thu, 13 Nov 2003, Lawrence, Mike (White Plains) wrote:

> Howard - maybe you don't realize it but you come off sounding quite
> arrogant and demeaning with some of your replies to people.  Read
> and think before you click the send button next time.

Perhaps.  But to Howard's defense, he is one of the most valuable
participants on this list and openldap community as a whole and I
interpret his responses as help.  Furthermore, answers to most of your
questions can easily be located in the openldap man pages, openldap
docs/faq and by searching google or other search engines.  The mailing
list should be used as a last resource for finding solutions.


> -----Original Message-----
> From: Howard Chu [mailto:hyc@symas.com]
> Sent: Thursday, November 13, 2003 4:02 PM
> To: 'Matthew Schumacher'; openldap-software@openldap.org
> Subject: RE: Problems with openldap-2.1.22 slowing down over time.
> > -----Original Message-----
> > From: owner-openldap-software@OpenLDAP.org
> > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Matthew
> Schumacher
> > Looks like I'm not the only one with index corruption/slow
> > down issues.
> >   Which debugging level shows backend and index interactions?  1024?
> Read the slapd(8) manpage.
> > What can I do to track this down?
> Read the Sleepycat documentation.
> > Perhaps this is a bdb tuning issue, but I would think that the
> > performance would be terrible all of the time, not just after we have
> > been running for a week.
> No. The BDB cache fills gradually as you process requests, it is not
> preloaded all at once. Use "db_stat -m" and see what your cache is doing,
> don't just sit there guessing in the dark.
>   -- Howard Chu
>   Chief Architect, Symas Corp.       Director, Highland Sun
>   http://www.symas.com               http://highlandsun.com/hyc
>   Symas: Premier OpenSource Development and Support
> This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged.
> The information is intended only for the use of the individual(s) or entity named above.  If you are not the intended recipient, be
> aware that any disclosure, copying or distribution or use of the contents of this information is prohibited.  If you have received
> this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.