From reading the documentation, it sounds like when configuring this
parameter you need to strike a balance between potential performance impact if it is too low, and wasted memory if it is too high. While running, is there any way to tell whether or not a search exceeded your configured value and required additional allocation? Whether via the monitor backend, or a log entry, or? Ideally, it would be nice to be able to tell if your configured value was too low and adjust as necessary.
Thanks.
Paul B. Henson wrote:
From reading the documentation, it sounds like when configuring this
parameter you need to strike a balance between potential performance impact if it is too low, and wasted memory if it is too high. While running, is there any way to tell whether or not a search exceeded your configured value and required additional allocation? Whether via the monitor backend, or a log entry, or? Ideally, it would be nice to be able to tell if your configured value was too low and adjust as necessary.
Since you mention that you're migrating from hdb, you can most likely ignore this parameter. It has the identical meaning in hdb after all, and if you never had to change it under hdb there's no reason to change it for mdb.
From: Howard Chu [mailto:hyc@symas.com] Sent: Wednesday, January 08, 2014 9:21 AM
Since you mention that you're migrating from hdb, you can most likely
ignore
this parameter. It has the identical meaning in hdb after all, and if you never had to change it under hdb there's no reason to change it for mdb.
Ah, it's been so long since I originally configured hdb, I didn't recognize it and mistakenly thought it was new. As you say, we've never had an issue with the default under hdb, so I will scratch that off my list, thanks much.
openldap-technical@openldap.org
-
Howard Chu -
Paul B. Henson