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

RE: slapd memory and performance problems



> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Mike Denka

> I'm thinking now after reading yours and Matthew Backes' explanation of
> memory utilization, and also since doubling the server RAM this morning
> to 1GB and discovering that the performance problem still exists, that
> this is not a memory problem but some other issue for which I yet have
> no explanation.  CPU utilization is very low.  Disk writes are numerous
> to the var partition where the ldap log file and the openldap database
> are, but reads to that partition are very low.

For optimum performance you must place the BDB logs on a separate physical
disk from the BDB data files. This is already stated in the BerkeleyDB
documentation.

> So am I correct in
> assuming that much data is cached (thus the high memory utilization by
> the threads)?

Yes.

> Then might the problem lie in the network connections?  I
> am currently seeing right around 100 connections, most in TIME_WAIT.  Is
> this something that could be corrected, at least in part, by unix
> sockets (ldapi:// url)?

Unix domain sockets only operate within a single machine. They are of no use
to you since you have 4 machines querying your LDAP server across a network.

You might re-read this message for some ideas:
http://www.openldap.org/lists/openldap-software/200303/msg00954.html

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support