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 ? Best Regards, Renato
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We were seeing similar CPU utilization recently. The problem turned out to be a lack of indexes. The web app for looking up people had changed recently and was doing substring matches on two attributes that were not indexed at all, much less for substrings. Once I created the indexes, CPU utilization dropped from 99% to under 2%. You might check your access logs to see what sorts of searches are being done and confirm that you have indexes in place to speed things up. -paul - --On Friday, January 26, 2007 10:18:25 AM -0200 Renato Ribeiro da Silva <capareci@uol.com.br> 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 ? > > Best Regards, > Renato > > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >- -- Paul D. Engle | Rice University Sr. Systems Administrator | Information Technology - MS119 (713) 348-4702 | P.O. Box 1892 pengle@rice.edu | Houston, TX 77251-1892 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFFuglNCpkISWtyHNsRAir0AKDzxxAfdzWuP8cENHFo08pWoHwfpgCg/YcK Nw7zT5Msb6b3eakxPaAOEys=mcCv -----END PGP SIGNATURE-----
I had this same problem, turned out that one of our analysts had a bad piece of code that was constantly querying the directory server for a username and password... Aaron -----Original Message----- From: fedora-directory-users-bounces@redhat.com [mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Renato Ribeiro da Silva Sent: Friday, January 26, 2007 7:18 AM To: fedora-directory-users Subject: [Fedora-directory-users] CPU utilization 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 ? Best Regards, Renato -- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users Confidentiality Notice: The information contained in this electronic message is intended for the exclusive use of the individual or entity named above and may contain privileged or confidential information. If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that dissemination, distribution or copying of this information is prohibited. If you have received this communication in error, please notify the sender immediately by telephone and destroy the copies you received.
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.
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 On 1/26/07, David Boreham <david_list@boreham.org> wrote:> > 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 > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >
Eddie C napisał(a):> 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.could You be more specific? How does this log entry looks like and where to turn on the indexes? I''ve searched a wiki but found noting (maybe I can''t find it ;) ). Any help would be appreciated :) -- xmpp/email: koniczynek@uaznia.net xmpp/email: koniczynek@gmail.com
Eddie C wrote:> 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.bin/slapd/admin/bin/logconv.pl can help diagnose some problems like this.> > Edward > > > > On 1/26/07, *David Boreham* <david_list@boreham.org > <mailto:david_list@boreham.org>> wrote: > > 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 > Fedora-directory-users@redhat.com > <mailto:Fedora-directory-users@redhat.com> > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >