On Thu, 20 Sep 2007, Alexander Wirt wrote: > P.S.: in fact switching off bdb makes amavis significant faster, so I will > think about it. On the other hand is changing the default behaviour of a > server a serious thing where all pros and cons should be calculated > carefully.
bdb requires that we properly configure its environment. I think amavis kills the bdb environment and re-creates it at every start, so it *must* configure the environment... So, yes, there might be a real misfeature in there. Are we setting the cache and locker region size to our real needs? Something to ask upstream, I suppose. Note that this depends on the number of maximum threads, but since we *do* know that number, we should tweak the bdb environment as needed. Notes about bdb environments: - changes only take effect on initial creation and db_recover - OpenLDAP seems to have the very best description of how to configure, so a search on openldap lists and docs will find some good stuff. a bdb environment. BDB documentation is... of poor quality here. - a DB_CONFIG file is the usual way to configure environments, but the BDB API has a set of calls you could use *before creating the environment* to set the parameters, as well. - the above is just some knowlege I gathered from maintaining cyrus imapd for so long, and keeping a close eye on openldap. Unfortunately, I don't know how to *really* properly program for BDB :) -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]