[Date Prev][Date Next]
RE: Memory Usage Spikes
--On Thursday, March 18, 2010 3:47 PM -0400 "Beuerlein, Edward"
Thanks for replying! Please let us know what other info you might need
to help us figure out these large increases in memory usage.
Here's the info you requested:
I did a dump of the database and then ran this on it(please let me know
if that isn't what you wanted):
# cat auth01.031610.ldif |grep dn |wc -l
So you have 60,753 entries. Just to be sure, I would have used grep ^dn:
to be exact. ;)
set_cachesize 0 268435456 1
You have 256MB allocated to BDB
Your BDB database is 2.9GB.
You're only allowing the first 1000 entries to be cached in OpenLDAP, and
your IdlCache is quite small as well. dncachesize is fine (unlimited).
While none of this explains your memory spikes, your server is definitely
poorly tuned. It may be that your massive discrepancy between BDB cache
allocation and actual BDB size may be causing the problem (in looking at
the bdb error messages in your log).
I would highly advise the following changes.
set_cachesize 4 0 1
This will increase the BDB cache to 4GB (which can hold your 2.9GB DB
This will allow all entries to be cached in OpenLDAP, free up a reasonable
number if you exceed the cache, and allow a decent IDL size.
I forgot to ask which slapd backend you are using (hdb or bdb), and which
version of BDB you are using (and if it is fully patched) which is also
You may also wish to read over
think you guys have some experience with Zimbra... ;)
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration