|
|
|
This report quantifies the total VM CPU resource consumption
in seconds per hour averaged across all processor engines and
within zone on the supporting computing system for a period
of five months. This is but another way to look at
percentage resource consumption. That is, if the average
number of CPU seconds consumed by each processor is 1800
seconds (out of a possible 3600 seconds), then approximately
50% of available processor capacity is being utilized.
The management objective to be tracked for evaluating the
rate of resource consumption for VM is the average CPU time
(in seconds) consumed per hour across a zone.
The only user option that applies to this report is the
Monthly VM CPU Consumption Amount, which is the target CPU
consumption (expressed in seconds) is used to set a reference
line on the graph.
&VMCMSAX defines the CPU consumption chart axis. &VMCMSRF
defines the target CPU consumption percentage. Therefore, to
define a target CPU consumption of 2700 CPU seconds per hour,
code:
%LET VMCMSAX = 3600;
%LET VMCMSRF = 2700;
A full description of the user options is provided in Section
3.3.4.1, VM Report Options.
Figure 3-59 illustrates the Monthly VM Resource Consumption
Report based on a management objective of consuming less than
2700 CPU seconds (on average) per hour during any given zone.
The sample report shown here quantifies the average seconds
of CPU consumption per hour within zone, with the horizontal
axis representing the zones of each month and the vertical
axis charting the average seconds of CPU time consumed per
processing engine across the hours falling within a given
zone.
The management objective for VM resource consumption is shown
by the dashed horizontal reference line printed across the
chart. In Figure 3-59, the reference line is shown at the
2700 CPU seconds consumed level of the vertical axis.
Therefore, any zone for which the charted bar exceeds this
reference line signals that the objective to contain resource
consumption was missed for that zone.
your_company_name 11:47 FRIDAY, JUNE 7, 1991 1 CA MICS I/S MANAGEMENT SUPPORT SYSTEM MONTHLY VM MANAGEMENT OBJECTIVES VM CPU RESOURCE CONSUMPTION (Unit: Seconds/Hour) SYSTEM=VM01 CPU 3600 + | | | 3240 + | | | 2880 + | *** | *** *** | *** *** *** 2520 + *** *** *** *** *** |--***--------------***--------------***--------------***--------------***--------------***------------------------ | *** *** *** *** *** *** | *** *** *** *** *** *** 2160 + *** *** *** *** *** *** | *** *** *** *** *** *** | *** *** *** *** *** *** | *** *** *** *** *** *** 1800 + *** *** *** *** *** *** | *** *** *** *** *** *** | *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** 1440 + *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** 1080 + *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 720 + *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 360 + *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ----------------------------------------------------------------------------------------------------------------- 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 ZONE |-- 90/12 --| |-- 91/01 --| |-- 91/02 --| |-- 91/03 --| |-- 91/04 --| |-- 91/05 --| YRMONTH (Reference Line: 2700 Seconds/Hour)
Figure 3-59. Monthly VM Resource Consumption
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |