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

Re: ITS#5860 slapd in openldap-2.4.16 still doesn't respect memory bounds

--On Friday, April 17, 2009 12:17 PM +0300 sscdvp@gmail.com wrote:

I have tried openldap-2.4.16 (latest) BDB 4.7.25 with all patches from
Oracle on Dell AMD64 RAM 4Gb, 8 CPUs, OS Solaris 10.
According to ITS#5860 slapd should not allocate more memory than it was
specified. In fact I have the same behaviour as it was with previous

version (2.4.11). It correctly allocates 1.2 Gb via shared memory (for
set_cachesize 300 MB). But slapd process continuosly grows in memory until
32-bit limit then crashes due to unavalable memory resources. I need to

mention bdb database size is less then 1 GB.
After restart it rapidly consumes 1.5 GB RSS in few minutes and then it
grows beyond the limit during 24 hours. The more queries are processing
the more memory it eats.

I am using this database for logging which size grows.
The question is: is it possible to use 32-bit openldap with relatively
large database sizes that override 32-bit per-process memory space?

My slapd.conf contains:

threads 64

Why do you have so many threads configured?  How many cpu's do you have??

Any help would be much appreciated.



Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Zimbra ::  the leader in open source messaging and collaboration