Re: OpenLDAP 2.4.23 killed by linux oom-killer

Michael Ströder wrote:

Quanah Gibson-Mount wrote:

...

b) Use an alternative memory allocated to glibc (for example, tcmalloc from the google perf tools suite, or hoard)

Glibc is extremely inefficient in managing memory for OpenLDAP, which only leads to substantial problems over time.

I guess this should also be not necessary anymore with back-mdb.

It should take many orders of magnitude longer for the problem to manifest, but even though the mdb backend is doing few/zero mallocs, the frontend still has malloc activity of its own.