we are still suffering from this poor performance problem. Any hint for
further debugging are welcome.
As this 389ds installation is part of an kolab multidomain setup we habe
about 50 separated database backends each replicated with two other servers.
The symtop is - depending on queries: sometimes everything is lacking
for several seconds (up to 3 or 4 and worse).
389ds is version 188.8.131.52-4 and runs on a xen 4.8 domU.
Load is not high neigher disk io at all. Everything else on the machine
or other xen-domains is running fine.
Am 28.05.2018 um 17:17 schrieb Jan Kowalsky:
> Hi all,
> while moving 389ds server to another machine (and another version) I
> realize performance issues during ldapsearch.
> Normaly a query ist quite quick (about 20ms - but sometimes(like every
> five seconds) it hangs for one ore even several seconds).
> I test this with:
> time ldapsearch -h localhost ...
> Since the new server should be a log faster (cpu, io) I'm wondering
> about what can cause this.
> There is a replication with three servers and suppier-supplier config
> among each. We have about 50 databases but each only maximum with a few
> hundred records. Most of them smaller.
> I looked for cache configuration - but these are similar to the old
> server and I get entrycachehitratio about 99%.
> Any idea for further debugging?
> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: