On Tue, 2018-03-13 at 13:05 -0500, Sergei Gerasenko wrote: > Sorry to resurrect this thread, but I’ve upgraded to 1.3.6 and so my > question is back on the table :) > > My cn=userRoot,cn=ldbm database,cn=plugins,cn=config is currently: > > ... > nsslapd-cachesize: -1 > nsslapd-cachememsize: 1543503872 > nsslapd-readonly: off > nsslapd-require-index: off > nsslapd-dncachememsize: 500000000 > … > > But cn=config,cn=ldbm database,cn=plugins,cn=config has these > settings: > ... > nsslapd-cache-autosize: 10 > nsslapd-cache-autosize-split: 40 > … > > If you remember, according to the docs, setting nsslapd-cache- > autosize to a value > 0, enables autosizing for all backends > regardless of their cache size settings. Is that accurate or must I > set them to 0s after all? It looks like autosizing is enforced > because I got an error when trying to modify the changelog backend: > > modifying entry "cn=changelog,cn=ldbm database,cn=plugins,cn=config" > ldap_modify: Server is unwilling to perform (53) > additional info: Error: "nsslapd-cachememsize" can not be > updated while "nsslapd-cache-autosize" is set in "cn=config,cn=ldbm > database,cn=plugins,cn=config". If autosize > 0, we write a new entrychace/cachememsize every start up. So you only need to set autosize to between 1 and 99 for it to work. There is some other logic in there to account for other scenarioes = for example, if you set autosize to 0 AND you set the entry cachesize to 0, we'll autosize it at start up anyway. BUT if you have autosize = 0, and entry cachesize > 0, we won't touch it. Does that help? > > Thanks! > > > On Mar 1, 2018, at 2:55 PM, Sergei Gerasenko <gerases@xxxxxxxxx> > > wrote: > > > > > I don't believe autotuning exists in 1.3.5, it was only added to > > > 1.3.6 - sorry :-/ > > > > Ah, that makes my life a bit simpler for now :) > > > > > > Also, is there a way to check that auto-tuning is working > > > > normally? Is dbmon.sh the right way? > > > The error log at startup will tell you what the server sets the > > > caches to. ldapsearch on nsslapd-dbcachesize will also return > > > the adjusted size if I am correct, but I haven't tried it. But > > > like I said before... this feature is not present in 389-ds-base- > > > 1.3.5 > > > > Got it. Thanks, Mark!! > > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@lists.fedoraproject.o > rg -- Thanks, William Brown _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
