--On Wednesday, October 28, 2020 5:34 PM +0000 [email protected] wrote:
Hi Paul,
A few things, after going back to your original email.
This is minor, but "pres" indices are useless unless < 50% of the database
has an instance of the attribute "pres" is being set on. I.e., setting
"pres" on objectClass is always useless, since it appears on every entry.
I am not sure what causes these log entries and if these are related to
higher CPU utilization. If you have any input/suggestions on where to
look next it would be much appreciated.
That just means an entry it's examining as part of the search result to a
query is not in scope. You can ignore it (and that's the reason why it
only shows up at a high debug level).
I would also note that since MDB is significantly more efficient, it can do
more in a given time slice than HDB. I.e., have you evaluated how many
searches/second are being process with MDB vs HDB? The ability to do more
in a given time slice means that MDB does generally use more CPU than HDB
-- but only because slapd is literally able to process more requests in a
given interval than HDB could. For example, in a test I did some years
ago (2013 or so), MDB could answer approximately 3x the number of
reads/second than HDB could (60k reads/sec vs just under 21k reads/second).
On more modern systems, the disparity is even more pronounced.
Outside of that, without more concrete information to work with, it's hard
to do anything other then speculate.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
