-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Kurt D.
Zeilenga
Other things to look at:
- ACLs... avoid unnecesary regex'ing
- REGEX... make sure you are using a good REGEX library
(some Solaris versions suck)
- Logging (disable synchronous logging, only log
minimal stuff)
Just echoing this - syslog() takes a huge toll on performance. On a
single-CPU machine with local log targets, the syslog daemon will eat up
more CPU and I/O resources than slapd itself. This is because syslogd
always flushes its disk buffers for every individual message it logs. I
haven't tested using a remote log destination; it may be cheaper since
the remote syslog protocol uses UDP, so there would be no filesystem
impact.
The fact that slapd is able to send debugging/diagnostic messages to
syslog() doesn't mean you should actually use this facility. Diagnostics
should only be generated when you are actively tracking down a problem,
and it's best just to use the "-d" option with stderr instead. Use of
syslog is best reserved for extraordinary situations, where system
integrity is in jeopardy and performance is no longer the issue...