how to resolve CPU bottleneck under hp-ux10.2

[zenari]

Hi,

I wonder how to resolve CPU bottleNeck on my old R380 server (180Mhz, 512 Mo RAM) running HP-UX 10.2.
The top command returns "0% idle" but I find it very hard to identify which process I need to kill. The server runs well on level 1.but slows down on run level 2, even with no user connected. Glance Plus is not installed on this machine ...
Any help to resolve this problem will be greatly appreciated

regards,
Olivier

[Sanjay_6]

Hi Olivier,

Check this doc from itrc, This is 1st part of 3 docs,

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063210674

The itrc doc id is S3100002312A.

The other two docs are S3100002312B & S3100002312C

It has a step by step procedure to do some troubleshooting for poor system performance.

Hope this helps.

Regds

[Bill Hassell]

CPU usage is easy to identify. The processes that are consuming all the cycles are listed in descending order by CPU load. Just kill the top processes...

Well, I have to explain that comment. If a process is using 100% CPU, and the process is not supposed to use that much, you call the programmer and get the code fixed. Now this ASSUMES that the system usage is 4-10%. If system sage is higher than 30%, there are a lot of steps that will be needed to identify the causes. There isn't anything you can do to the kernel--it is doing what it was asked to do.

If you have remote logins over the network, it is very common for untrained users to trash their connections and leave orphaned processes that loop around trying to talk to the LAN. You'll need to kill those processes.

[Victor BERRIDGE]

Hi Olivier,
Here I must agree with Bill, so at level 2 unless someone messed around your inits by adding some non OS start script and dont laugh Ive seen this a few times, IF system load >40% of CPU usage and it lasts or gets worse you will have to double check what you have in /etc/inittab, what is beeing executed and if what is beeing executed has changed. Then knowinf that is slows down at level 2, comment out all the start/stop and gradually uncomment till you find the guilty script.
If still you havent solve your issue, its most likely to be something wrong with/in /etc/inittab

Isnt the anything in /var/adm/syslog/syslog.log or /etc/rc.log ?

Good luck and Merry Christmas
Victor