Just to share experience with the community, my problem was related to
idlcachesize, that was (relatively) too small for the dimension of my db. I
augmented that value to a very larger value and performances increases very
much.
Just to give a concrete example of what I'm saying, my purge job
Hi all,
I would like to know the internal behaviour of slapo-accesslog.
I would like to have accesslog with a data retention of 10 days. In my ldap
usage scenario this retention produce an accesslog db of quite 10GB of data.
Things are working quite fine, but when the log db contains data older
Marco Pizzoli wrote:
Hi all,
I would like to know the internal behaviour of slapo-accesslog.
Read the slapo-accesslog(5) manpage. Re-read the logpurge description and
don't skip any of it.
I would like to have accesslog with a data retention of 10 days. In my ldap
usage scenario this
Hi Howard,
probably you are addressing me to this part:
When using a log database that supports ordered indexing on generalizedTime
attributes, specifying an eq index on the* reqStart* attribute will greatly
benefit the performance of the purge operation.
My accesslog db is back-hdb and I have
