--On Wednesday, March 18, 2020 6:16 PM +0000 Markus.Storm(a)t-systems.com
we're currently testing performance of OpenLDAP on Oracle/RedHat Linux
and quite unexpected actually hit systemd-journald to be a bottleneck.
While OpenLDAP happily makes use of all available CPUs, that one is
single threaded, braking everything. The only way around I have found is
to set olcLoglevel to 0, speeding up my test run by a factor of 6(!).
That now of course is not an option to use in production.
I'd happily directly write to a file as I did in the old days but I
cannot get olcLogfile to work. And even if I was able to get there, how
do I stop OpenLDAP from logging to syslogd (which is inevitably
forwarding everything to system-journald ….) ?
Can anyone give advice how to handle this ? Any hint appreciated (short
of "get a decent OS" – that is not an option).
We always advise our customers to disable the abominable syslog<->journald
integration that RedHat has pushed onto their customers with complete
disregard to the consequences of this short-sighted action. Not only does
it destroy performance, it can also cause the system to completely deadlock.
If you need instructions on how to do this, let me know.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: