Alcatel 5620 Troubleshooting Manual page 122

7 — Troubleshooting Solaris and Windows platforms
Heading
mjf
xcal
intr
ithr
csw
icsw
migr
smtx
srw
syscl
usr
sys
wt
idl
(2 of 2)
6
7-4
Description (events per second unless noted)
Major faults
Interprocessor cross-calls
Interrupts
Interrupts as threads (not counting clock interrupts)
Context switches
When the csw number slowly increases and the platform is not I/O bound, a
mutex contention is indicated
Involuntary context switches
When the iscw number increases beyond 500, the system is considered to be
under heavy load
Thread migrations to another processor
Spins on mutexes (lock not acquired on first try)
if the smtx number increases sharply, for instance from 30 to 300, a system
resource bottleneck is indicated
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.
Alcatel 5620 Service Aware Manager, Release 2.1 R2
May 2005 95-5887-01-00-B