27.12.2012 Views

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

14.1.1 Using the INDICATE command<br />

z/<strong>VM</strong> has some basic commands such as INDICATE. <strong>The</strong>re are many INDICATE parameters that<br />

can be included as command line options. Use the command HELP INDICATE <strong>for</strong> a basic<br />

understanding and then press F11 <strong>for</strong> help on each parameter.<br />

INIDICATE LOAD<br />

If no parameter is specified INDICATE LOAD is the default option. <strong>The</strong>re are two flavors of this,<br />

depending on whether the issuing user ID has privilege class G or class E. Class G users can<br />

use INDICATE to display recent contention <strong>for</strong> system resources, display environment<br />

characteristics and measurements of resources used by their virtual machine.<br />

<strong>The</strong> output from user ID with class E privilege (e.g. MAINT, OPERATOR) is shown here. <strong>The</strong> lines<br />

are number <strong>for</strong> clarity of the description that follows:<br />

==> ind load<br />

1 AVGPROC-038% 03<br />

2 XSTORE-000021/SEC MIGRATE-0001/SEC<br />

3 MDC READS-000068/SEC WRITES-000001/SEC HIT RATIO-099%<br />

4 PAGING-0031/SEC STEAL-000%<br />

5 Q0-00006(00000) DORMANT-00357<br />

6 Q1-00001(00000) E1-00000(00000)<br />

7 Q2-00001(00000) EXPAN-002 E2-00000(00000)<br />

8 Q3-00034(00000) EXPAN-002 E3-00000(00000)<br />

9<br />

<strong>10</strong> PROC 0000-038% PROC 0001-038%<br />

11 PROC 0002-038%<br />

12<br />

13 LIMITED-00000<br />

<strong>The</strong> INDICATE LOAD command gives a snapshot of current system per<strong>for</strong>mance. Except <strong>for</strong> the<br />

counts of virtual machines in various queues and the limited list, the values you see here are<br />

a smoothed average over the past 4 minutes. Areas where z/<strong>VM</strong> per<strong>for</strong>mance analysts tend<br />

to focus are the following:<br />

► AVGPROC on line 1 gives the overall processor utilization, 38% in this example. <strong>The</strong> number<br />

following it is the number of on-line processors, 3 in this example. <strong>The</strong> individual processor<br />

utilization is shown on lines <strong>10</strong> and 11. Take a glance at these to see if they are somewhat<br />

balanced. <strong>The</strong>re are cases where an imbalance is okay. This would include very low<br />

utilization scenarios or cases where there are not enough users ready to run virtual<br />

processors to keep the physical processors busy. One of the processors will be a Master,<br />

all of the others Alternate, and some imbalance may result from per<strong>for</strong>ming these<br />

functions. Line 2 describes paging to expanded storage. Most z/<strong>VM</strong> systems on z9 class<br />

machines can sustain several <strong>10</strong>00s of this type of paging operations a second without<br />

any problems. z<strong>10</strong> class machines will per<strong>for</strong>m even better. <strong>The</strong> MIGRATE rate is the<br />

number of pages per second being moved from expanded storage out to paging space on<br />

DASD. A healthy system will have a MIGRATE rate significantly lower than the XSTORE rate,<br />

probably being measures in <strong>10</strong>0s rather than <strong>10</strong>00s. <strong>The</strong> higher values seen tend to build<br />

up over time, and are sustained over periods of intense system activity, however, there<br />

are times the MIGRATE value may spike <strong>for</strong> brief periods of time.<br />

► Minidisk cache (MDC) statistics are given on the third line. <strong>The</strong> effectiveness of MDC can be<br />

judged by the combination of the READS rate and the HIT RATIO. If both are high, then a<br />

large number of physical I/Os are avoided due to the MDC feature. For a system which<br />

has an appreciably high I/O rate, composed of reads plus writes, and a high proportion of<br />

reads, and a good hit ratio <strong>for</strong> those reads (tending to 90% or greater), the real, physical<br />

I/O avoidance can be very high, this author has seen the avoidance as high as 50% in<br />

some cases. Conversely, however, a high HIT RATIO with a low value <strong>for</strong> the READS rate<br />

224 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!