<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sys-Admin Information&#039;s &#187; AIX</title>
	<atom:link href="http://sysinfo.bascomp.org/category/aix/feed/" rel="self" type="application/rss+xml" />
	<link>http://sysinfo.bascomp.org</link>
	<description></description>
	<lastBuildDate>Fri, 23 Apr 2010 09:43:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Performance Monitoring Commands</title>
		<link>http://sysinfo.bascomp.org/2007/07/performance-monitoring/</link>
		<comments>http://sysinfo.bascomp.org/2007/07/performance-monitoring/#comments</comments>
		<pubDate>Thu, 05 Jul 2007 17:02:00 +0000</pubDate>
		<dc:creator>Eriek Regandono</dc:creator>
				<category><![CDATA[AIX]]></category>

		<guid isPermaLink="false">http://sysinfo.bascomp.org/2007/07/05/performance-monitoring/</guid>
		<description><![CDATA[ Monitoring Commands
nmon
vmstat
iostat
sar
topas
nmon
svmon
filemon
rmss

nmon
More info bout nmon
http://www-128.ibm.com/developerworks/aix/library/au-analyze_aix/
vmstat
The vmstat command is useful for obtaining an overall picture of CPU, paging, and memory usage.
 $ vmstat 5 2
System Configuration: lcpu=2 mem=8192MB
kthr     memory             page          [...]]]></description>
			<content:encoded><![CDATA[<p> Monitoring Commands<br />
nmon<br />
vmstat<br />
iostat<br />
sar<br />
topas<br />
nmon<br />
svmon<br />
filemon<br />
rmss</p>
<p><span id="more-14"></span><br />
<strong>nmon</strong><br />
More info bout nmon<br />
http://www-128.ibm.com/developerworks/aix/library/au-analyze_aix/</p>
<p><strong>vmstat</strong><br />
The vmstat command is useful for obtaining an overall picture of CPU, paging, and memory usage.</p>
<blockquote><p> $ <strong>vmstat 5 2</strong><br />
System Configuration: lcpu=2 mem=8192MB<br />
kthr     memory             page              faults        cpu<br />
----- ----------- ------------------------ ------------ -----------<br />
r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa<br />
1  1 287340   317   0   0   0 124  261   0 265  261 122  2  0 97  0<br />
0  0 287344   313   0   0   0   0    0   0 228  491  76  0  0 99  0</p></blockquote>
<p>Remember that the first report from the vmstat command displays cumulative activity since the last system boot. The second report shows activity for the first 5-second interval.</p>
<p><strong>iostat</strong><br />
The iostat command is the fastest way to get a first impression, whether or not the system has a disk I/O-bound performance problem. This tool also reports CPU statistics.</p>
<blockquote><p> Flags -a  Specifies adapter throughput report.<br />
-d  Specifies drive report only.<br />
-m Specifies statistics for paths.<br />
-t  Specifies tty/cpu report only.<br />
-z Resets the disk input/output statistics.</p>
<p>$ <code>iostat 2 2</code><br />
System configuration: lcpu=2 disk=20</p>
<p>tty:      tin         tout   avg-cpu:  % user    % sys     % idle    % iowait<br />
0.0          1.0               1.9      0.4       97.5       0.3</p>
<p>Disks:        % tm_act     Kbps      tps    Kb_read   Kb_wrtn<br />
hdisk1           0.8     133.9      12.7   1221182814  13264883<br />
hdisk0           1.1     148.9       6.5   913739775  459468711<br />
hdisk8           0.0       0.0       0.0          0         0</p></blockquote>
<p><strong>svmon</strong><br />
The svmon command provides a more in-depth analysis of memory usage. It is more informative, but also more intrusive, than the vmstat and ps commands. The svmon command captures a snapshot of the current state of memory.<br />
The memory consumption is reported using the inuse, free, pin, virtual and paging space counters.</p>
<ul>
<li>The <em>inuse</em> counter represents the number of used frames.</li>
<li>The <em>free</em> counter represents the number of free frames from all memory pools.</li>
<li>The <em>pin</em> counter represents the number of pinned frames, that is, frames that cannot be swapped.</li>
<li>The <em>virtual</em> counter represents the number of pages allocated in the system virtual space.</li>
<li>The <em>paging space</em> counter represents the number of pages reserved or used on paging spaces.</li>
</ul>
<blockquote><p> Flags<br />
-G   Global report<br />
-U   User report<br />
-P   Process report<br />
-i   To define intervel and number of intervels. eg. -i 1 5</p></blockquote>
<p>A memory leak can be detected with the svmon command, by looking for processes whose working segment continually grows. A leak in a kernel segment can be caused by an mbuf leak or by a device driver, kernel extension, or even the kernel. To determine if a segment is growing, use the svmon command with the -i option to look at a process or a group of processes and see if any segment continues to grow.</p>
<blockquote><p>  # <code>svmon -P 13548 -i 1 2</code><br />
Pid                         Command        Inuse        Pin      Pgsp  Virtual 64-bit Mthrd LPage 13548                       pacman         8535        2178      847     8533      N     N     NVsid     Esid Type  Description          LPage Inuse    Pin  Pgsp  Virtual0       0 work  kernel seg               -   4375   2176   847     437548412       2 work  process private          -   <strong>2357     2    0    2357</strong>6c01b       d work  shared library text      -   1790      0     0     1790</p>
<p>4c413       f work  shared library data      -     <strong>11     0    0      11</strong></p>
<p>3040c       1 pers  code,/dev/prodlv:4097    -      2      0     -        -</p>
<p>ginger :svmon -P 13548 -i 1 3</p>
<p>Pid                         Command        Inuse        Pin      Pgsp  Virtual 64-bit Mthrd LPage</p>
<p>13548                       pacman         8589         2178       847  8587      N     N     N</p>
<p>Vsid     Esid Type  Description          LPage  Inuse    Pin  Pgsp  Virtual</p>
<p>0        0 work  kernel seg               -   4375   2176   847     4375</p>
<p>48412       2 work  process private          -   <strong>2411     2    0    2411</strong></p>
<p>6c01b       d work  shared library text      -   1790      0     0     1790</p>
<p>4c413       f work  shared library data      -     <strong>11     0    0      11</strong></p>
<p>3040c       1 pers  code,/dev/prodlv:4097    -      2      0     -        -</p></blockquote>
<p><strong>filemon</strong><br />
The <strong>filemon</strong> command monitor a trace for file system and IO system events and reports performance statistics for files, virtual memory segments, logical volumes and physical volumes. <strong>filemon</strong> is useful to those whose applications are believed to be disk-bound and want to know where and why.<br />
<strong>filemon</strong> command shows the load on different disks, logical volumes and files in a great detail.<br />
<strong>trcstop</strong> command is used to stop the filemon monitoring.<br />
The syntax of filemon command is</p>
<blockquote><p> filemon [-o output_file] [-O levels] [-u] [-v]<br />
-O [lv | pv | vm | If | all ]<br />
(If - Logical file level, vm - Virtual memory level, lv - lv level)<br />
-u Reports on files that were opened prior to the start of the trace daemon</p></blockquote>
<p>If the output file is not specified, the output is sent to standard output.<br />
To start the filemon monitoring for 1 min.</p>
<blockquote><p> # <code>filemon -uo filemon.out -O all ; sleep 60; trcstop</code></p></blockquote>
<p>To find out the most active Logical Volumes</p>
<blockquote><p> # <code>awk '/Most Active Logical Volumes/,/^$/' filemon.out</code><br />
Most Active Logical Volumes-------------------------------------------------<br />
util  #rblk  #wblk   KB/s  volume                   description<br />
------------------------------------------------------------------------<br />
0.04   4208      0   34.9  /dev/paging00            paging</p>
<p>0.04   4000      0   33.2  /dev/hd6                 paging</p>
<p>0.01   1680  11408  108.6  /dev/oralvr32            /oracle/R32</p>
<p>0.00      0    264    2.2  /dev/hd8                 jfs2log</p></blockquote>
<p>To find out most active Files</p>
<blockquote><p> # <code>awk '/Most Active Files/,/^$/' filemon.out</code></p></blockquote>
<p>To find out most active physical Volumes</p>
<blockquote><p>  # <code>awk '/Most Active Physical Volumes/,/^$/' filemon.out</code></p></blockquote>
<p><strong>rmss</strong><br />
The <strong>rmss</strong> command provides you with a means to simulate different sizes of real memory that are smaller than your actual machine, without having to extract and replace memory boards or reconfigure memory using logical partitions.<br />
To change the memory size to 500 MB</p>
<blockquote><p>  # <code>rmss -c 500 </code><br />
Simulated memory size changed to 500 Mb.</p></blockquote>
<p>To reset the memory size to the real memory size of the machine, enter:</p>
<blockquote><p>   # <code>rmss -r </code></p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://sysinfo.bascomp.org/2007/07/performance-monitoring/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
