[Kolab-devel] Re: OpenLDAP performance issues

[Dieter Kluenter]

Hi 
Martin,

Martin Konold <martin.konold at erfrakon.de> writes:

> Am Freitag, 20. Mai 2005 10:39 schrieb Dieter Kluenter:
>
> Hi Dieter,
>
>> 2. change to hdb backend, as this is optimized for search operations,
>>    but lack performance on heavy write operations.
>
> Is hdb supposed to get us rid of the bdb problems?

I don't think you have a general problem with OpenLDAP and any backend
which could not be solved by proper configuration.
The back-hdb is an improvement of back-bdb and designed for optimised
search operations. 

> What about tdb?

I don't know.

> Why does OpenLDAP not offer to autmatically tune the DB parameters?

In OpenLDAP-2.3 configuration is moved to a config backend, which
allows changes to configuration parameters at runtime.

> Dieter: Is the following FAQ entry still valid?
> http://www.openldap.org/faq/data/cache/756.html
> (Unfortunately all of these optimizations aren't always visible at the user 
> level, because the BDB transaction subsystem adds considerable overhead to 
> back-bdb. For the most part the fanatical tuning efforts in back-bdb only 
> bring it on par with back-ldbm in terms of performance.) 

This faq entry refers to OpenLDAP-2.0 and 2.1 and BerkeleyD-4.0.x
While the general description of back-bdb vs. back-ldbm is still
valid, BerkeleyDB-4.2.x offers better transaction handling and
back-bdb has been improved.

-Dieter

-- 
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:01443B53