If it's installed, try top. This should give you the top 10 processes which are grabbing resources. As an alternative, the following script (provided by someone else here, but I can't recall who, sorry to whoever it was!) will do much the same thing:
which will show processes in order of CPU usage a page at a time, with the highest usage at the top of the list. Ignore the kproc at the top (one for each processor) which is the 'soak' process and will use all unused CPU cycles.
You may find something at the top of this list with is a dead giveaway.
If you don't, then it is time to do some more digging, and this is where things get a bit more vague.
Try
vmstat 3 20 which will take a snapshot every 3 seconds for 1 minute (do this while the system is struggling). You will see output like the following... (i've messed with the columns a bit to avoid wrap around.
kthr memory page faults cpu
----- ----------- ---------------- --------- -----------
r b avm fre re pi po fr sr cy in sy cs us sy id wa
If you look at the last four columns, us, sy, id and wa, then these represent User, System, Idle, and Waiting as percentages (all 4 columns add up to 100).
If the us + sy columns > 80 consistently, then you are probably suffering from a CPU bottleneck, i.e. your RS6000 just doesn't have the CPU power to handle the workload you are putting on it.
If the wa column is consistently non-zero, this may indicate an I/O bottleneck on disk.
If the id column is consistently high, then this would indicate that your problem is not down to high CPU usage.
Also look at the pi / po columns under the 'page' heading. If these are consistently non-zero, this indicates that your system is low in memory (check the fre column) and is paging heavily, which will seriously impact on performance.
If your wa column indicates a lot of waiting for I/O to complete use this command...
iostat 3 20 (again while the system is struggling) and like vmstat, this will take a snapshot every 3 seconds for a minute, and will give output like this for each snapshot
tty: tin tout avg-cpu:% user % sys % idle % iowait
9.0 327.7 19.7 44.6 23.7 11.9
As a general rule of thumb, your system is I/O bound if your %iowait > 25% and %tm_act > 70% on any given disk.
Hopefully this will give you some pointers to start looking. If you try this on your system and post any output here, I will gladly try and troubleshoot your system for you.
Regards, LHLTech
IBM CS - AIX V4.3 System Support
Halfway through CATE exams!
If you are running AIX 4.3.3 you could also try 'topas' or 'nmon' both are excellent tools for monitoring the system - and both have switches to check top processes.
hi ken i tried running the same script but it returns to the prompt wo anything......can u tell y....??????? Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
yup lhl.....the paths to head and ps were different.....thanx for the advice...also, thanx ken for this script.....and i think everythings fair in computer world....beg....borrow...steal....!!! Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.