Alcatel-Lucent 5620 Troubleshooting Manual page 240

8 — Troubleshooting Solaris and Windows platforms
Heading
srw
syscl
usr
sys
wt
idl
(2 of 2)
5
Procedure 8-2 Problem: Slow performance on a Solaris workstation,
but no spike or peak in the CPU
A platform is disk or I/O bound when it continuously services requests for data from a
disk, and other activities must wait for those requests to complete. You can determine
whether a machine is disk or I/O bound using the iostat command. You can also perform
the following procedures:
8-4
Description (events per second unless noted)
Spins on readers/writer locks (lock not acquired on first try)
System calls
Percent user time
Percent system time
Percent wait time
Percent idle time
Review the usr, sys and idl data. Together, these three outputs indicate CPU
saturation. A Java application fully using the CPUs should fall within 80 to 90
percent of the usr value, and 20 to 10 percent of the sys value. A smaller
percentage for the sys value indicates that more time is being spent running
user code, which generally results in better execution of the Java
application.
As well, when the smtx output is high on a multiple CPU system, this
indicates that CPUs are competing for resources.
iii Press ESC-Q to quit or CTRL-C to stop the mpstat command.
If processes are competing for CPU resources, you can isolate the information
about a single process using the ps command.
i Check the state of CPUs by typing:
/usr/ucb/ps -aux ↵
A list of processes appears.
ii Review the ps output.
For CPU troubleshooting, the important data is listed in the %CPU row. If a
process is taking 90% or more of the CPU resources, there may be a problem
with the process. Contact your account or technical support representative
for more information.
iii Press ESC-Q to quit or CTRL-C to stop the ps command.
Aug 2010
Troubleshooting Guide
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
8.0 R4