[389-users] Re: autosizing the cache

2018-03-21 Thread William Brown
> > > dbmon.sh > Tue Mar 20 02:16:04 UTC 2018 > dbcachefree 432873472 free% 80.629 roevicts 0 hit% 99 pagein 1267 > pageout 23191 > changelog:ent 616509293897 100.0 4359.2 > changelog:dn29262999793332 100.070.6 > userroot:ent 117776408341275 98.4

[389-users] Re: autosizing the cache

2018-03-19 Thread Sergei Gerasenko
Hi William, > On Mar 19, 2018, at 9:18 PM, William Brown wrote: > > yeah, dncachesize is manual. But I think dncachesize is per backend, > not part of cn=config,cn=ldbm plugin. Yes, I see one for changelog and one for userRoot. Here’s the data: > dbscan -f

[389-users] Re: autosizing the cache

2018-03-19 Thread William Brown
On Mon, 2018-03-19 at 20:58 -0500, Sergei Gerasenko wrote: > > Dogtag is Java/Tomcat. It's well known for consuming large volumes > > of > > ram! > > Ah, I thought it was something besides that :) Nope, just that :) > > > Sure, sounds reasonable to me - I'd want to see your database sizes > >

[389-users] Re: autosizing the cache

2018-03-19 Thread Sergei Gerasenko
> Dogtag is Java/Tomcat. It's well known for consuming large volumes of > ram! Ah, I thought it was something besides that :) > Sure, sounds reasonable to me - I'd want to see your database sizes to > make a complete assesment, but it seems pretty reasonable to me. I will get that for you.

[389-users] Re: autosizing the cache

2018-03-19 Thread William Brown
On Sun, 2018-03-18 at 21:57 -0500, Sergei Gerasenko wrote: > Thank you for the detailed response, William. That’s great info. You > mentioned FreeIPA in passing and that’s actually what I use 389-ds > for. You mentioned dogtag eating memory. You mean it has a memory > leak or some other memory

[389-users] Re: autosizing the cache

2018-03-18 Thread Sergei Gerasenko
Thank you for the detailed response, William. That’s great info. You mentioned FreeIPA in passing and that’s actually what I use 389-ds for. You mentioned dogtag eating memory. You mean it has a memory leak or some other memory mismanagement issue? I have 125G of RAM on my systems. So, I can

[389-users] Re: autosizing the cache

2018-03-18 Thread William Brown
On Tue, 2018-03-13 at 21:10 -0500, Sergei Gerasenko wrote: > Hi William, > > With autosizing on I configured the changelog backend: > > dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config > cn: changelog > objectClass: top > objectClass: extensibleObject > objectClass: nsBackendInstance >

[389-users] Re: autosizing the cache

2018-03-13 Thread Sergei Gerasenko
Hi William, With autosizing on I configured the changelog backend: dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config cn: changelog objectClass: top objectClass: extensibleObject objectClass: nsBackendInstance nsslapd-suffix: cn=changelog nsslapd-cachesize: -1 nsslapd-cachememsize:

[389-users] Re: autosizing the cache

2018-03-13 Thread William Brown
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:

[389-users] Re: autosizing the cache

2018-03-13 Thread Sergei Gerasenko
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

[389-users] Re: autosizing the cache

2018-03-01 Thread Sergei Gerasenko
> 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

[389-users] Re: autosizing the cache

2018-03-01 Thread Mark Reynolds
On 03/01/2018 03:18 PM, Sergei Gerasenko wrote: > 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?| |I don't believe autotuning exists in 1.3.5, it was only added to

[389-users] Re: autosizing the cache

2018-03-01 Thread Sergei Gerasenko
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

[389-users] Re: autosizing the cache

2018-03-01 Thread Mark Reynolds
On 03/01/2018 02:32 PM, Sergei Gerasenko wrote: > Hello, > > 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: 5 > … > > But