The best way to handle performance issues is look in the acccess log for notes=U. These are unindexed searches. Its amazing to add the index and then watch the processor move from 99% to 0% thats what happened with one of our applications. It is definately a good idea to make different usernames for you different applications. If you give each application a different login it later allows you to go back and write individual ACI's. If all your applications share the same login you will eventually have to move all applications to a different user. Here is a question for all. Does anyone know of a log tool specifically for LDAP logs? I think there are big possibilites for something like this. Edward <div>On 1/26/07, David Boreham <<a href="mailto:david_list@boreham.org">david_list@boreham.org</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Renato Ribeiro da Silva wrote: >I'm having questions about CPU utilization of Directory Server. The process ns-slapd take 99.9% of CPU almost all the time. Is there any way to know why this is happening? Any performance counter ( DS Console ) can show me the answer ? Is is possible to know the apps that are using the Directory in this moment ? > > Look in the access log. If there is an application loading the server then its operations will show up in quantity in the log. Also try running the 'pstack' command on the slapd process. This will give you a stack trace for where the CPU is being burned, which in turn may indicate the cause. -- Fedora-directory-users mailing list <a href="mailto:Fedora-directory-users@redhat.com">Fedora-directory-users@redhat.com </a> <a href="https://www.redhat.com/mailman/listinfo/fedora-directory-users">https://www.redhat.com/mailman/listinfo/fedora-directory-users</a> </blockquote></div>