Cool. The default setup of 389-ds (version 1.3.5.10) I don’t see either
nsslapd-cache-autosize or nsslapd-cache-autosize-split. Should I just add them
to the dse file?
> Correct, set them to 0 for autotuning to take effect
The Redhat docs are a bit confusing on this
(https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/performance_tuning_guide/memoryusage
<https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/performance_tuning_guide/memoryusage>):
> nsslapd-cache-autosize
> This settings controls if auto-sizing is enabled for the database and entry
> cache. Auto-sizing is enabled:
> For both the database and entry cache, if the nsslapd-cache-autosize
> parameter is set to a value greater than 0.
> For the database cache, if the nsslapd-cache-autosize and nsslapd-dbcachesize
> parameters are set to 0.
> For the entry cache, if the nsslapd-cache-autosize and
> nsslapd-cachememsizeparameters are set to 0.
You just confirmed bullet 2 and 3. But bullet 1 is not clear: if I
setnsslapd-cache-autosize to something greater than 0 and both types of caches
become auto-tuned, why would then I need to set them to 0 (to enable
auto-tuning) individually?
Also, is there a way to check that auto-tuning is working normally? Is dbmon.sh
the right way?
Thanks again,
Sergei
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
