Академический Документы
Профессиональный Документы
Культура Документы
This presentation focuses on the tactical -- meaning your daily “keyboard awareness”.
This will explain the numbers presented by AIX commands (vmstat, mpstat, iostat, ps,
etc.) and formulate the severity of performance issues, if any.
Note the size, scale, technology and implementation of the given LPAR
Note the LPAR’s ratio-of-resources, ie. CPU-to-RAM-to-SAN I/O for the workload
Note the same of other same-frame “sibling” LPARs, if any
Monitor dynamic AIX behaviors using a 1 or 2 second sampling interval (vs >30secs)
Verify a stressful workload exists: “We can’t tune what is not being taxed”
Discontinue active efforts when done: “If/when it runs fast enough, we’re tuned”
Build with track-able discrete structures: “We can’t tune what can’t be tracked”
Monitor spikes,peaks,bursts and burns: “We tune the intensities, not the sleepy-times”
Establish dynamic baselines by monitoring real-time AIX behaviors by ranges&ratios
Watch AIX behaviors with the goal of characterizing the workload (vmstat –Iwt 2)
System Configuration: lcpu=48 mem=174080MB
Note the size, scale, technology and implementation of the given LPAR
Note the LPAR’s ratio-of-resources, i.e. CPU-to-RAM-to-SAN I/O
Network Information
Host Name: alamogordo
IP Address: addr
Sub Netmask: mask
Gateway: gateway
Name Server: nameserv
Domain Name: domain
$ lsps -a
Page Space Physical Volume Volume Group Size %Used Active Auto Type
paging01 hdisk80 pagingvg 32736MB 1 yes yes lv
paging01 hdisk81 pagingvg 32736MB 1 yes yes lv
paging00 hdisk78 pagingvg 32736MB 1 yes yes lv
paging00 hdisk79 pagingvg 32736MB 1 yes yes lv
hd6 hdisk0 rootvg 512MB 0 no yes lv
$ lsps -s
Total Paging Space Percent Used
130944MB 1%
$ mount
node mounted mounted over vfs date options
-------- --------------- --------------- ------ ------------ ---------------
/dev/hd4 / jfs Oct 20 22:06 rw,log=/dev/hd8
/dev/hd2 /usr jfs Oct 20 22:06 rw,log=/dev/hd8
/dev/hd9var /var jfs Oct 20 22:06 rw,log=/dev/hd8
/dev/hd3 /tmp jfs Oct 20 22:06 rw,log=/dev/hd8
/dev/hd1 /home jfs Oct 20 22:08 rw,log=/dev/hd8
/proc /proc procfs Oct 20 22:08 rw
/dev/hd10opt /opt jfs Oct 20 22:08 rw,log=/dev/hd8
/dev/lvsapcds /sapcds jfs2 Oct 20 22:08 rw,log=/dev/lv00
/dev/lvcnvbt /cnv jfs2 Oct 20 22:20 rw,log=/dev/lvjfs00
/dev/lvhrtmpbt /hrtmp jfs2 Oct 20 22:20 rw,log=/dev/lvjfs00
/dev/lvoraclebt /oracle jfs2 Oct 20 22:20 rw,log=/dev/lvjfs00
/dev/lvorapr1bt /oracle/PR1 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs00
/dev/lvmirrlogAp /oracle/PR1/mirrlogA jfs2 Oct 20 22:20 rw,log=/dev/lvjfs20
/dev/lvmirrlogBp /oracle/PR1/mirrlogB jfs2 Oct 20 22:20 rw,log=/dev/lvjfs20
/dev/lvoriglogAp /oracle/PR1/origlogA jfs2 Oct 20 22:20 rw,log=/dev/lvjfs20
/dev/lvoriglogBp /oracle/PR1/origlogB jfs2 Oct 20 22:20 rw,log=/dev/lvjfs20
/dev/lvsaparchbt /oracle/PR1/saparch jfs2 Oct 20 22:20 rw,log=/dev/lvjfs00
/dev/lvsapdata1bt /oracle/PR1/sapdata1 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs01
/dev/lvsapdata18bt /oracle/PR1/sapdata10 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs10
/dev/lvsapdata11bt /oracle/PR1/sapdata11 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs11
/dev/lvsapdata24bt /oracle/PR1/sapdata12 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs12
/dev/lvsapdata2bt /oracle/PR1/sapdata2 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs02
/dev/lvsapdata3bt /oracle/PR1/sapdata3 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs03
/dev/lvsapdata14bt /oracle/PR1/sapdata4 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs04
/dev/lvsapdata23bt /oracle/PR1/sapdata5 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs05
/dev/lvsapdata16bt /oracle/PR1/sapdata6 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs06
/dev/lvsapdata7bt /oracle/PR1/sapdata7 jfs2 Oct 20 22:20 rw,log=/dev/lvjfs07
…
… © 2010 IBM Corporation
AIX Virtual Users Group presentation July 29, 2010
$ ipcs -bm | wc -l
164
$ ipcs -bm | grep -v sapsys
IPC status from /dev/mem as of Sun Mar 2 16:23:03 PST 2008
T ID KEY MODE OWNER GROUP SEGSZ
Shared Memory:
m 1048576 0xffffffff --rw-rw---- root system 8192
m 1048577 0xffffffff --rw-rw---- root system 4096
m 1048578 0x7800004f --rw-rw-rw- root system 16777216
m 3 0xffffffff --rw-rw---- root system 4096
m 4 0x670017bc --rw-r--r-- root system 12
m 5 0x680017bc --rw-r--r-- root system 106548
m 6 0x700017bc --rw------- root system 3152
m 7 0xffffffff --rw-rw---- root 219 4096
m 62914569 0x8aa6abe8 --rw-r----- orapr1 dba 12903030784
$ ipcs -bm | grep -c sapsys
152
$ ipcs -bm | grep sapsys
m 23068682 0xffffffff --rw-r----- pr1adm sapsys 1024
m 11 0x0382be84 --rw-rw-rw- pr1adm sapsys 4096
m 46137357 0xffffffff --rw------- pr1adm sapsys 2147483648
m 46137358 0xffffffff --rw------- pr1adm sapsys 2147483648
m 53477391 0xffffffff --rw------- pr1adm sapsys 2147483648
m 44040210 0xffffffff --rw------- pr1adm sapsys 2147483648
m 44040211 0xffffffff --rw------- pr1adm sapsys 2147483648
m 51380244 0xffffffff --rw------- pr1adm sapsys 2147483648
m 51380254 0xffffffff --rw------- pr1adm sapsys 2147483648
m 57671711 0x00002725 --rw-r----- pr1adm sapsys 562192
m 56623136 0x00002722 --rw-r----- pr1adm sapsys 656416
m 56623137 0xffffffff --rw------- pr1adm sapsys 2147483648
m 54525986 0xffffffff --rw------- pr1adm sapsys 2147483648
m 42991653 0xffffffff --rw------- pr1adm sapsys 2147483648
…
vmstat –s # Writes to standard output the contents of the sum structure, which
contains an absolute count of paging events since system initialization.
[ Continued ]
vmstat –s # [continued] Writes to standard output the contents of the sum structure,
which contains an absolute count of paging events since system initialization.
backtracks
Incremented for each page fault that occurs while resolving a previous page fault. (The new page fault must be resolved
first and then initial page faults can be backtracked.)
free frame waits
Incremented each time a process requests a page frame, the free list is empty, and the process is forced to wait while
the free list is replenished.
extend XPT waits
Incremented each time a process is waited by VMM due to a commit in progress for the segment being accessed.
pending I/O waits
Incremented each time a process is waited by VMM for a page-in I/O to complete.
start I/Os
Incremented for each read or write I/O request initiated by VMM.
iodones
Incremented at the completion of each VMM I/O request.
CPU context switches
Incremented for each processor context switch (dispatch of a new process).
device interrupts
Incremented on each hardware interrupt.
software interrupts
Incremented on each software interrupt. A software interrupt is a machine instruction similar to a hardware interrupt that
saves some state and branches to a service routine. System calls are implemented with software interrupt instructions
that branch to the system call handler routine.
decrementer interrupts
Incremented on each decrementer interrupt.
…
[ Continued ]
iostat –a # cumulative since last boot; Create a complete tech-stack map, ie.
RAIDset/tech->LUN->[LVMvg:lv::JFS2mtpt w/options]->logical_content
System configuration: lcpu=24 drives=48 ent=1.20 paths=268 vdisks=0 tapes=38
tty: tin tout avg-cpu: % user % sys % idle % iowait physc % entc
0.1 35.5 65.7 31.4 1.0 1.9 0.2 17.7
vgname = rootvg
pv_pbuf_count = 512
total_vg_pbufs = 1024
max_vg_pbuf_count = 16384
pervg_blocked_io_count = 0
pv_min_pbuf = 512
global_blocked_io_count = 176559
vgname = oravg
pv_pbuf_count = 512
total_vg_pbufs = 8192
max_vg_pbuf_count = 16384
pervg_blocked_io_count = 176559
pv_min_pbuf = 512
global_blocked_io_count = 176559
…
…
netstat –ss # cumulative since last boot; displays only non-zero values (this is
an undocumented command-option of netstat)
$ netstat -ss
ip:
343290037 total packets received
257309 fragments received
5 fragments dropped after timeout
128641 packets reassembled ok98
$ netstat -v
…
…
-------------------------------------------------------------
ETHERNET STATISTICS (ent7) :
Device Type: EtherChannel
Hardware Address: 00:14:5e:48:c1:cc
Elapsed Time: 134 days 0 hours 21 minutes 27 seconds
General Statistics:
-------------------
No mbuf Errors: 0
Adapter Reset Count: 0
Adapter Data Rate: 2000
…
…
© 2010 IBM Corporation
AIX Virtual Users Group presentation July 29, 2010
nfsstat # cumulative since last boot; displays server and client NFS statistics
$ nfsstat
Server rpc:
Connection oriented
calls badcalls nullrecv badlen xdrcall dupchecks dupreqs
715102799 128 0 0 0 58378077 20
Connectionless
calls badcalls nullrecv badlen xdrcall dupchecks dupreqs
536 0 0 0 0 0 0
Server nfs:
calls badcalls public_v2 public_v3
715102602 27 0 0
Version 2: (256 calls)
null getattr setattr root lookup readlink read
256 100% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
wrcache write create remove rename link symlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
mkdir rmdir readdir statfs
0 0% 0 0% 0 0% 0 0%
Version 3: (715102346 calls)
null getattr setattr lookup access readlink read
208 0% 56755889 7% 1397024 0% 430178070 60% 4733070 0% 0 0% 55037597 7%
write create mkdir symlink mknod remove rmdir
43093505 6% 2409219 0% 7 0% 0 0% 0 0% 2329235 0% 14 0%
rename link readdir readdir+ fsstat fsinfo pathconf
110306 0% 63 0% 17771684 2% 9038704 1% 65544670 9% 206 0% 95 0%
commit
26702780 3%
Client rpc:
Connection oriented
calls badcalls badxids timeouts newcreds badverfs timers
272059 0 0 0 0 0 0
nomem cantconn interrupts
0 0 0
Connectionless
calls badcalls retrans badxids timeouts newcreds badverfs
79 0 0 0 0 0 0
timers nomem cantsend
0 0 0
…
… © 2010 IBM Corporation
AIX Virtual Users Group presentation July 29, 2010
ps -el | wc
ps -elmo THREAD | wc
ps -kl | wc
ps -klmo THREAD | wc
857 11953 81517 # 857 user procs (one line of column header)
PID TTY STAT TIME PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND
0 - A 359:49 7 384 384 xx 0 0 0.0 0.0 swapper
1 - A 2:58 112 688 736 32768 32 48 0.0 0.0 /etc/init
8196 - A 1355:41 0 384 384 xx 0 0 0.1 0.0 wait
12294 - A 4:11 0 448 448 xx 0 0 0.0 0.0 sched
16392 - A 0:50 0 1216 1216 xx 0 0 0.0 0.0 lrud
20490 - A 0:00 0 448 448 xx 0 0 0.0 0.0 vmptacrt
…
192694 - A 231:54 25933 492 500 xx 3 8 0.0 0.0 /usr/sbin/syncd 60
…
1921222 - A 1:12 0 448 448 xx 0 0 0.0 0.0 aioserver
1945664 - A 1:27 0 448 448 xx 0 0 0.0 0.0 aioserver
1954040 - A 0:01 6502 14184 7704 32768 39 112 0.0 0.0 db2agent (CICP75) 0
1958100 - A 0:00 0 2708 1924 32768 39 112 0.0 0.0 db2agent (CICP75) 0
1962154 - A 0:00 0 2804 1700 32768 39 112 0.0 0.0 db2agent (CICP75) 0
1982616 - A 0:03 7630 21912 14920 32768 39 112 0.0 0.0 db2agent (CICP75) 0
1990804 - A 0:09 35673 20560 15488 32768 39 112 0.0 0.0 db2agent (CICP75) 0
1998936 - A 0:21 18151 11576 7656 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2003126 - A 11:16 0 384 384 xx 0 0 0.0 0.0 wait
2007224 - A 0:07 20302 23108 15988 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2023454 - A 131:32 37058 7372 7420 32768 39 112 0.1 0.0 db2ckpwd 0
2027608 - A 0:08 25717 13248 7792 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2031778 - A 0:01 4392 17400 8296 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2056344 - A 1:22 0 448 448 xx 0 0 0.0 0.0 aioserver
2072818 - A 0:01 789 11080 7736 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2089120 - A 0:10 35352 19668 14596 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2105366 - A 0:04 16649 20856 15016 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2117646 - A 0:02 3150 14996 6340 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2126002 - A 0:00 456 11380 4772 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2129984 - A 0:15 16343 13100 7196 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2150502 - A 0:00 6 3892 2916 32768 39 112 0.0 0.0 db2agent (CICP75) 0
2158720 - A 0:02 4948 15320 7304 32768 39 112 0.0 0.0 db2agent (CICP75) 0
$ vmstat –I 2
System configuration: lcpu=24 mem=73728MB ent=12.00
kthr
Number of kernel threads in various queues averaged per second over the sampling
interval. The kthr columns are as follows:
–r
Average number of kernel threads that are runnable, which includes threads that are
running and threads that are waiting for the CPU. If this number is greater than the
number of CPUs, then there is at least one thread waiting for a CPU and the more
threads there are waiting for CPUs, the greater the likelihood of a performance impact.
–b
Average number of kernel threads in the VMM wait queue per second. This includes
threads that are waiting on filesystem I/O or threads that are blocking on a shared
resource, i.e. inode-lock.
–p
For vmstat -I The number of threads waiting on I/Os to raw devices per second. Threads
waiting on I/Os to filesystems would not be included here.
memory
Provides information about the real and virtual memory.
– avm
The Active Virtual Memory, avm, column represents the number of active virtual memory
pages present at the time the vmstat sample was collected. It is the sum-total of all
computational memory – including content paged-out to the pagingspace. The avm
statistics do not include file pages.
– fre
The fre column shows the average number of free memory pages. A page is a 4 KB area
of real memory. The system maintains a buffer of memory pages, called the free list, that
will be readily accessible when the VMM needs space. The minimum number of pages
that the VMM keeps on the free list is determined by the minfree parameter of the vmo
command.
– fo
The fo column details the number of pages paged-out to persistent storage, i.e. pages
written-out to JFS/JFS2 file systems on disk. This does not include pagingspace-
pageout’s to the pagingspace ; rather, these are filesystem-writes.
Page (continued)
Information about page faults and paging activity. These are averaged over the interval and given in units
per second.
– pi
The pi column details the number of pages paged in from paging space. Paging space is the part of
virtual memory that resides on disk. It is used as an overflow when memory is over committed. Paging
space consists of logical volumes dedicated to the storage of working set pages that have been stolen
from real memory. When a stolen page is referenced by the process, a page fault occurs, and the
page must be read into memory from paging space.
Due to the variety of configurations of hardware, software and applications, there is no absolute number
to look out for. This field is important as a key indicator of paging-space activity. If a page-in occurs,
there must have been a previous page-out for that page. It is also likely in a memory-constrained
environment that each page-in will force a different page to be stolen and, therefore, paged out.
– po
The po column shows the number (rate) of pages paged out to paging space. Whenever a page of
working storage is stolen, it is written to paging space, if it does not yet reside in paging space or if it
was modified. If not referenced again, it will remain on the paging device until the process terminates
or disclaims the space. Subsequent references to addresses contained within the faulted-out pages
results in page faults, and the pages are paged in individually by the system. When a process
terminates normally, any paging space allocated to that process is freed. If the system is reading in a
significant number of persistent pages, you might see an increase in po without corresponding
increases in pi. This does not necessarily indicate thrashing, but may warrant investigation into data-
access patterns of the applications.
© 2010 IBM Corporation
AIX Virtual Users Group presentation July 29, 2010
page (continued)
Information about page faults and paging activity. These are averaged over the interval and
given in units per second.
– fr
Number of pages that were freed per second by the page-replacement algorithm during
the interval. As the VMM page-replacement routine scans the Page Frame Table, or
PFT, it uses criteria to select which pages are to be stolen to replenish the free list of
available memory frames. The criteria include both kinds of pages, working
(computational) and file (persistent) pages. Just because a page has been freed, it does
not mean that any I/O has taken place. For example, if a persistent storage (file) page
has not been modified, it will not be written back to the disk. If I/O is not necessary,
minimal system resources are required to free a page.
– sr
Number of pages that were examined per second by the page-replacement algorithm
during the interval. The page-replacement algorithm might have to scan many page
frames before it can steal enough to satisfy the page-replacement thresholds. The higher
the sr value compared to the fr value, the harder it is for the page-replacement algorithm
to find eligible pages to steal.
faults
Information about process control, such as trap and interrupt rate. The faults columns are as follows:
– in
Number of device interrupts per second observed in the interval.
– sy
The number of system calls per second observed in the interval. Resources are available to user
processes through well-defined system calls. These calls instruct the kernel to perform operations for
the calling process and exchange data between the kernel and the process. Because workloads and
applications vary widely, and different calls perform different functions, it is impossible to define how
many system calls per-second are too many. But typically, when the sy column raises over 10000
calls per second on a uniprocessor, further investigations is called for (on an SMP system the number
is 10000 calls per second per processor). One reason could be "polling" subroutines like the select()
subroutine. For this column, it is advisable to have a baseline measurement that gives a count for a
normal sy value.
– cs
Number of context switches per second observed in the interval. The physical CPU resource is
subdivided into logical time slices of 10 milliseconds each. Assuming a thread is scheduled for
execution, it will run until its time slice expires, until it is preempted, or until it voluntarily gives up
control of the CPU. When another thread is given control of the CPU, the context or working
environment of the previous thread must be saved and the context of the current thread must be
loaded. The operating system has a very efficient context switching procedure, so each switch is
inexpensive in terms of resources. Any significant increase in context switches, such as when cs is a
lot higher than the disk I/O and network packet rate, should be cause for further investigation.
cpu
Percentage breakdown of CPU time usage during the interval. The cpu columns are as follows:
– us
– The us column shows the percent of CPU time spent in user mode. A UNIX® process can execute in either user mode
or system (kernel) mode. When in user mode, a process executes within its application code and does not require
kernel resources to perform computations, manage memory, or set variables.
– sy
– The sy column details the percentage of time the CPU was executing a process in system mode. This includes CPU
resource consumed by kernel processes (kprocs) and others that need access to kernel resources. If a process needs
kernel resources, it must execute a system call and is thereby switched to system mode to make that resource
available. For example, reading or writing of a file requires kernel resources to open the file, seek a specific location,
and read or write data, unless memory mapped files are used.
– id
– The id column shows the percentage of time which the CPU is idle, or waiting, without pending local disk I/O. If there
are no threads available for execution (the run queue is empty), the system dispatches a thread called wait, which is
also known as the idle kproc. On an SMP system, one wait thread per processor can be dispatched. The report
generated by the ps command (with the -k or -g 0 option) identifies this as kproc or wait. If the ps report shows a high
aggregate time for this thread, it means there were significant periods of time when no other thread was ready to run or
waiting to be executed on the CPU. The system was therefore mostly idle and waiting for new tasks.
– wa
– The wa column details the percentage of time the CPU was idle with pending local disk I/O and NFS-mounted disks. If
there is at least one outstanding I/O to a disk when wait is running, the time is classified as waiting for I/O. Unless
asynchronous I/O is being used by the process, an I/O request to disk causes the calling process to block (or sleep)
until the request has been completed. Once an I/O request for a process completes, it is placed on the run queue. If
the I/Os were completing faster, more CPU time could be used.
– A wa value over 25 percent could indicate that the disk subsystem might not be balanced properly, or it might be the
result of a disk-intensive workload.
$ uptime ; mpstat -d 2
03:06PM up 133 days, 17:58, 2 users, load average: 5.87, 4.92, 4.66
cpu cs ics bound rq push S3pull S3grd S0rd S1rd S2rd S3rd S4rd S5rd ilcs vlcs
0 1387 947 0 0 0 0 0 86.9 0.2 0.0 12.9 0.0 0.0 0 1317
1 4 2 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0 0 1359
2 1165 752 0 0 0 0 0 85.2 0.2 0.0 14.6 0.0 0.0 0 883
3 0 0 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0 0 576
4 868 576 0 0 0 0 0 83.5 0.3 0.0 16.3 0.0 0.0 0 801
5 3 2 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0 0 882
6 1259 813 0 0 0 0 0 84.9 0.1 0.0 14.9 0.0 0.0 0 1091
7 2 2 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0 0 1113
8 1207 809 0 0 0 0 0 85.5 0.0 0.0 14.5 0.0 0.0 0 1082
9 0 0 0 0 0 0 0 - - - - - - 0 1099
10 990 654 0 0 0 0 0 87.0 0.0 0.0 13.0 0.0 0.0 0 804
11 0 0 0 0 0 0 0 - - - - - - 0 802
12 1388 907 0 0 0 0 0 89.4 0.0 0.0 10.6 0.0 0.0 0 986
13 0 0 0 0 0 0 0 - - - - - - 0 990
14 1104 730 0 0 0 0 0 86.7 0.0 0.0 13.3 0.0 0.0 0 949
15 0 0 0 0 0 0 0 - - - - - - 0 960
16 659 411 0 0 0 0 0 88.8 0.0 0.0 11.2 0.0 0.0 0 524
17 0 0 0 0 0 0 0 - - - - - - 0 589
18 863 452 0 0 0 0 0 96.1 0.0 0.0 3.9 0.0 0.0 0 215
19 0 0 0 0 0 0 0 - - - - - - 0 316
20 1175 766 0 0 0 0 0 87.1 0.0 0.0 12.9 0.0 0.0 0 943
21 0 0 0 0 0 0 0 - - - - - - 0 951
22 1224 705 0 0 0 0 0 91.8 0.0 0.0 8.2 0.0 0.0 0 635
23 0 0 0 0 0 0 0 - - - - - - 0 639
ALL 13298 8528 0 0 0 0 0 87.7 0.1 0.0 12.2 0.0 0.0 0 20506
------------------------------------------------------------------------------------------------------
cpu cs ics bound rq push S3pull S3grd S0rd S1rd S2rd S3rd S4rd S5rd ilcs vlcs
0 1969 1277 0 0 0 0 0 83.2 0.0 0.0 16.8 0.0 0.0 0 1940
1 0 0 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0 0 1968
2 1679 1068 0 0 0 0 0 85.7 0.0 0.0 14.3 0.0 0.0 0 1216
3 0 0 0 0 0 0 0 - - - - - - 0 1236
…
cpu cs ics bound rq push S3pull S3grd S0rd S1rd S2rd S3rd S4rd S5rd
0 1232 816 0 0 0 0 0 84.8 0.0 6.9 8.3 0.0 0.0
1 0 0 0 0 0 0 0 - - - - - -
2 2080 1179 0 0 0 1 0 91.6 0.0 3.4 4.9 0.0 0.0
3 0 0 0 0 0 0 0 - - - - - -
4 1614 989 0 0 0 1 0 89.9 0.0 4.4 5.6 0.0 0.1
5 0 0 0 0 0 0 0 - - - - - -
6 2180 1317 0 0 0 1 0 91.9 0.0 3.5 4.6 0.0 0.1
7 0 0 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0
8 159 110 0 0 0 2 0 98.4 0.0 0.0 0.0 1.6 0.0
9 0 0 0 0 0 0 0 - - - - - -
10 127 96 0 0 0 2 0 97.6 0.0 0.0 0.0 2.4 0.0
11 0 0 0 0 0 0 0 - - - - - -
ALL 7392 4507 0 0 0 7 0 90.5 0.0 4.0 5.3 0.1 0.0
------------------------------------------------------------------------------------------------------------------------------------
0 1815 1058 0 0 0 0 0 95.0 0.0 2.0 3.0 0.0 0.0
1 0 0 0 0 0 0 0 - - - - - -
2 1543 897 0 0 0 0 0 95.1 0.0 2.0 3.0 0.0 0.0
3 0 0 0 0 0 0 0 - - - - - -
4 1593 997 0 0 0 0 0 92.7 0.0 3.7 3.7 0.0 0.0
5 0 0 0 0 0 0 0 - - - - - -
6 2031 1193 0 0 0 0 0 94.8 0.0 2.7 2.5 0.0 0.0
7 0 0 0 0 0 0 0 - - - - - -
8 21 11 0 0 0 0 0 100.0 0.0 0.0 0.0 0.0 0.0
9 0 0 0 0 0 0 0 - - - - - -
10 4 4 0 0 0 0 0 - - - - - -
11 0 0 0 0 0 0 0 - - - - - -
ALL 7007 4160 0 0 0 0 0 94.5 0.0 2.6 3.0 0.0 0.0
------------------------------------------------------------------------------------------------------------------------------------
© 2010 IBM Corporation
AIX Virtual Users Group presentation July 29, 2010
tty: tin tout avg-cpu: % user % sys % idle % iowait physc % entc time
0.0 62.1 92.4 4.8 0.3 2.6 11.8 98.6 15:42:10
aio: avgc avfc maxg maif maxr avg-cpu: % user % sys % idle % iowait
32 0 223 0 8192 21.1 7.8 46.5 24.5
aio: avgc avfc maxg maif maxr avg-cpu: % user % sys % idle % iowait
0 0 215 0 8192 18.8 7.7 49.1 24.4
…
02:18PM up 223 days, 15:57, 5 users, load average: 2.00, 2.54, 2.88
3955510096 total address trans. faults
663204206 page ins
2212345555 page outs
146844573 paging space page ins
136603972 paging space page outs
0 total reclaims
1876773643 zero filled pages faults
29655645 executable filled pages faults
3363959830 pages examined by clock
819733 revolutions of the clock hand
1565374921 pages freed by the clock
82564968 backtracks
5138 free frame waits
0 extend XPT waits
2353814111 pending I/O waits
2859262790 start I/Os
2376968599 iodones
50335935279 cpu context switches
16475063625 device interrupts
1149300248 software interrupts
8545158185 decrementer interrupts
88508563 mpc-sent interrupts
88508328 mpc-receive interrupts
1247188423 phantom interrupts
0 traps
223061804590 syscalls
lsps –a
lsps –s
mount
df –k
ipcs –bm
vmo –L
ioo -L
uptime; vmstat –s
uptime; vmstat –v
uptime ; ps -ekf | egrep "syncd|lrud|nfsd|biod|wait"
iostat –a
iostat –D
vmstat –v | grep pbuf
for VG in `lsvg`; do; lvmo -a -v $VG; echo; done
netstat –ss
netstat –v
nfsstat
topas <cr> d n c c
ps –kelmo THREAD
ps guww
ps gvww
vmstat –Iwt 2
mpstat –w 2
mpstat –dw 2
iostat –aT 2
iostat -AQ 2
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.
Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market.
Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.
*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA,
WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
* All other products may be trademarks or registered trademarks of their respective companies.
Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will
experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual
environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without
notice. Consult your local IBM business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance,
compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.
Disclaimers
No part of this document may be reproduced or transmitted in any form without written permission from IBM
Corporation.
Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change
without notice. This information could include technical inaccuracies or typographical errors. IBM may make
improvements and/or changes in the product(s) and/or program(s) at any time without notice. Any statements
regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals
and objectives only.
The performance data contained herein was obtained in a controlled, isolated environment. Actual results that may be
obtained in other operating environments may vary significantly. While IBM has reviewed each item for accuracy in
a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customer
experiences described herein are based upon information and opinions provided by the customer. The same
results may not be obtained by every user.
Reference in this document to IBM products, programs, or services does not imply that IBM intends to make such
products, programs or services available in all countries in which IBM operates or does business. Any reference to
an IBM Program Product in this document is not intended to state or imply that only that program product may be
used. Any functionally equivalent program, that does not infringe IBM's intellectual property rights, may be used
instead. It is the user's responsibility to evaluate and verify the operation on any non-IBM product, program or
service.
THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER
EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR INFRINGEMENT. IBM shall have no responsibility to update this information. IBM
products are warranted according to the terms and conditions of the agreements (e.g. IBM Customer Agreement,
Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. IBM
is not responsible for the performance or interoperability of any non-IBM products discussed herein.
Disclaimers Continued
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products in connection with this
publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those
products.
The providing of the information contained herein is not intended to, and does not, grant any right or license under
any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
USA
IBM customers are responsible for ensuring their own compliance with legal requirements. It is the customer's sole
responsibility to obtain advice of competent legal counsel as to the identification and interpretation of any relevant
laws and regulatory requirements that may affect the customer's business and any actions the customer may need
to take to comply with such laws.
IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is
in compliance with any law.
The information contained in this documentation is provided for informational purposes only. While efforts were made
to verify the completeness and accuracy of the information provided, it is provided “as is” without warranty of any
kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise
related to, this documentation or any other documentation. Nothing contained in this documentation is intended to,
nor shall have the effect of, creating any warranties or representations from IBM (or its suppliers or licensors), or
altering the terms and conditions of the applicable license agreement governing the use of IBM software.
Thank You
Earl Jew
IBM Field Technical Sales Specialist for Power Systems and Storage
IBM Regional Designated Specialist - Power/AIX Performance & Tuning
400 North Brand Blvd., Suite 700 c/o IBM, Glendale, CA, USA 91203
earlj@us.ibm.com (310)251-2907