[389-users] Re: performance tuning

> cn=config is special, that's why :) You should generally ignore it for > these discussions about backends and databases. not to annoy, but what’s special about it? A quick question about the terminology: what’s a backend? The physical db files on disk? > So if you look at the entries from

[389-users] Re: performance tuning

On Mon, 2017-11-20 at 09:42 -0600, Sergei Gerasenko wrote: > Hi William, > > > So to really answer that I should explain the LDAP data model. > > > > You have a set of objects, in a tree database. The RootDSE (you can > > search with -b '' -s base by the way with ldapsearch) is the ... > > well,

[389-users] Re: performance tuning

Hi William, > So to really answer that I should explain the LDAP data model. > > You have a set of objects, in a tree database. The RootDSE (you can > search with -b '' -s base by the way with ldapsearch) is the ... well, > root. Under than you have "suffixes", like dc=com and >

[389-users] Re: performance tuning

On Thu, 2017-11-16 at 21:59 -0600, Sergei Gerasenko wrote: > Hi William, > > Thanks much for the quick response! This is super helpful. I’m > attaching my cpu and meminfo info. Sorry for the late response: was travelling, > > > > dn: cn=monitor,cn=ldbm database,cn=plugins,cn=config > > > > ^

[389-users] Re: performance tuning

The change went in and the machine’s cache rate is currently at 91. woot! > On Nov 17, 2017, at 11:46 AM, Sergei Gerasenko wrote: > > Thanks, Mark!! > >> On Nov 17, 2017, at 10:58 AM, Mark Reynolds > > wrote: >> >> >>

[389-users] Re: performance tuning

Thanks, Mark!! > On Nov 17, 2017, at 10:58 AM, Mark Reynolds wrote: > > > > On 11/17/2017 11:45 AM, Sergei Gerasenko wrote: >> dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config >> changetype: modify >> replace: nsslapd-dncachememsize >> nsslapd-dncachememsize:

[389-users] Re: performance tuning

On 11/17/2017 11:45 AM, Sergei Gerasenko wrote: > dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config > changetype: modify > replace: nsslapd-dncachememsize > nsslapd-dncachememsize: 30 > - > replace: nsslapd-cachememsize > nsslapd-cachememsize: 30 After these changes you do

[389-users] Re: performance tuning

Here’s my emergency ldif for now: dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config changetype: modify replace: nsslapd-dncachememsize nsslapd-dncachememsize: 30 - replace: nsslapd-cachememsize nsslapd-cachememsize: 30 dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config

[389-users] Re: performance tuning

Hi William,Thanks much for the quick response! This is super helpful. I’m attaching my cpu and meminfo info.dn: cn=monitor,cn=ldbm database,cn=plugins,cn=config^ This monitors the general BDB performance.Got it.dn: cn=monitor,cn=changelog,cn=ldbm database,cn=plugins,cn=configdn:

[389-users] Re: performance tuning

On Thu, 2017-11-16 at 21:00 -0600, Sergei Gerasenko wrote: > Hi, > > I’ve been trying to estimate how optimal our settings are. I’ve read > about the cn=monitor section and I see that there are several paths > that have cn=monitor: These are all monitors for each database backend. So you have: