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

RE: LDAP, bdb, don't want log files for replication

If you are using a 4.2 release of BerkeleyDB, (preferably 4.2.52 + patches) you may disable transaction logging by putting these two lines in your DB_CONFIG file:

set_flags       DB_TXN_NOSYNC
set_flags       DB_TXN_NOT_DURABLE

You cannot do this with the 4.3 releases of BerkeleyDB.

To me, turning on the logs sounds like madness (but my use case of openldap is quite different from most) because the performance penalty is far to severe, so to each his own.


-----Original Message-----
From: owner-openldap-software@OpenLDAP.org [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Adam Tauno Williams
Sent: Monday, April 18, 2005 11:32 AM
To: openldap-software@OpenLDAP.org
Subject: Re: LDAP, bdb, don't want log files for replication

> I need a very very fast LDAP server.
> I actually use OpenLDAP with bdb, and I notice that most of the time is
> taken to write logs for recovery/replication (file log.000000XXXXX).
> I don't need this files, and I searched on the web to tune bdb with no
> success. I had only found option about cache size, but it's not sufficient.
> How can I run an OpenLdap server without generating this files ?

I've collected what performance tuning notes I could find in -

The best approach to me seems to be putting the database and longs on seperate
sets of spindles, that helps allot.  Honestly, turning of the logs sounds like
madness to me.