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
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
