Willian, 

Cache values from cn=config + cn=userRoot: https://paste.fedoraproject.org/paste/ZqmA2wUkQDcSUaUIcpGDhg
free -h + lspcu: https://paste.fedoraproject.org/paste/Br8Vz5-quxtcatiDyMy3QA

I'll check it out the docs for the optimization + wait until your response, i think it will more secure.

Thanks.

Em seg, 14 de ago de 2017 às 20:24, William Brown <wibrown@redhat.com> escreveu:
On Mon, 2017-08-14 at 18:24 +0000, Lucas Diedrich wrote:
> Willian, sorry for the time i took to answers, in the attachment there is
> the gstack.out. I don't have a clue how to read that =/
>

No problem, it's my job to know how to read it :)

THere are a lot of threads in:

#11 0x00007fb6487f3795 in __db_get_pp () from /lib64/libdb-5.3.so
#12 0x00007fb643a355fb in id2entry ()
from /usr/lib64/dirsrv/plugins/libback-ldbm.so
#13 0x00007fb643a3171d in dn2entry_ext ()
from /usr/lib64/dirsrv/plugins/libback-ldbm.so

Are your dbcache, dncache and entrycache settings large enough? This
issue could be indicative of cache thrashing,


Besides that, nothing indicates specifically that the issue is MO.

https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/performance_tuning_guide/determining-req-cache-size

This part of the performance tuning guide may help you. If you want, you
can send me the output of your objects:

cn=conficn=config,cn=ldbm database,cn=plugins,cn=configg,cn=ldbm
database,cn=plugins,cn=config

dn: cn=config,cn=ldbm database,cn=plugins,cn=config
dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config

And the output of free -h and lscpu.



--
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane

_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org