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

RE: Réf. : RE: LDAP, bdb, don't want log files for replication

Information on those flags is out there somewhere on the openLDAP's site... Like most of the other advanced configuration information.  Knowing that that is what you are looking for, and finding it is the trick, as you discovered.

I wish that the option was supported in the newer releases of BerkeleyDB as well - but this isn't openLDAP's fault.  As I understand it, the 4.3 release of BerkeleyDB is just flat out broken in this respect, and they (the maintainers of BerkeleyDB) won't fix it.

I'm not sure what I will do in the future if OpenLDAP starts requiring a newer version of BerkeleyDB - because the performance with logging turned on is horrible for the way that I use it (like you, as a hierarchical database for large amounts of recreatable information).  Maybe I could set up a RAM disk, and put the logs on that...


-----Original Message-----
From: owner-openldap-software@OpenLDAP.org [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of ST21@ineo.com
Sent: Tuesday, April 19, 2005 2:23 AM
To: Armbrust, Daniel C.
Cc: openldap-software@OpenLDAP.org; owner-openldap-software@OpenLDAP.org
Subject: Réf. : RE: LDAP, bdb, don't want log files for replication

Thank you, it's working.
Maybe it will be a good idea to convert this documentation in html and to
include it in the openldap site ?
I use OpenLDAP for scientific calculations (I need a hierarchic database,
and I don't have time to program it), and my datas are not important, I can
recalculate them. But I need a very fast OpenLDAP for writing.
Without logs, the write process is 20X faster.
Maybe you may keep this DB config flags in future versions ?

                      "Armbrust, Daniel C."                                                                                                     
                      <Armbrust.Daniel@mayo.edu         Pour :   openldap-software@OpenLDAP.org                                                 
                      >                                 cc :     (ccc : ST21/GTMH)                                                              
                      Envoyé par :                      Objet :  RE: LDAP, bdb, don't want log files for replication                            
                      18/04/2005 20:07                                                                                                          

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

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
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
> 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
sets of spindles, that helps allot.  Honestly, turning of the logs sounds
madness to me.