Rolling 4-Hour MSU Usage Distribution Section
In this example, 0.4% of four-hour periods consumed more than 33 MSU per hour. If the defined capacity is set at 33 MSU per hour, it is projected that the partition is capped by Workload Manager 0.8% of the time. In other words, if you would like the partition to be capped 0.8% of the time, set the defined capacity of the partition at 33 MSU per hour.
If a partition already has defined capacity, you can adjust its value by using this section and the % Capped by WLM column ( % WLM) in the Partition Data Section.
Calculation method for PROJECTED % CAPPED BY WLM
Every five minutes, Workload Manager calculates the MSU per hour usage averaged over the previous four-hour period. If the average exceeds the defined capacity, the partition is capped for the next five minutes; that is, it can only use as much CPU as set by defined capacity. At the end of this (next) five-minute period, Workload Manager calculates the four-hour average again. If it drops below defined capacity, the capping is removed; otherwise, the partition stays capped.
Similarly, CMF calculates the four-hour MSU per hour average for the end of every recording interval n. If the average exceeds the tentative defined capacity, the partition is considered capped for the entire length of the next recording interval n+1. (If the partition used more than the defined capacity in this next interval, the excess usage is charged to the following interval n+2.) At the end of the recording interval n+1, CMF calculates the four-hour average again. If it drops below tentative defined capacity, the partition is no longer considered capped.
An example of the Rolling 4-Hour MSU Usage Distribution Section of the CPU Utilization Report is shown in the following figure.
BMC SOFTWARE, INC. BMC SOFTWARE, INC. REPORT DATE: 10 SEP 16 23.21
ACTL 04 SEP 16 11.30.00 08 SEP 16 15.00.01 HOUSTON, TX. SYSTEM ID: SJSC Z 2.02.0
BASED ON REC TYPE/# RECS/# SAMPLES/REC HOURS: 70-1/396/356K/98.79
----------------------------------------- ROLLING 4-HOUR MSU USAGE DISTRIBUTION SECTION ------------------------------------------
CPU FAMILY: 2964 VERSION: 00 MODEL: 514 CEC CAPACITY = 1,000
PARTITION = SJSC NUMBER OF 4-HOUR PERIODS = 334
CONSUMED MSU 98 95 92 89 86 83 80 77 74 71
----- ----- ----- ----- ----- ----- ----- ----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 2.1 3.3 3.9 4.2 4.8 5.1 5.7 6.3 6.6 6.9
CONSUMED MSU 68 65 62 59 56 53 51
----- ----- ----- ----- ----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 7.5 7.8 8.4 8.7 9.3 9.6 10.2
PARTITION = CF11 NUMBER OF 4-HOUR PERIODS = 0
PARTITION = CF12 NUMBER OF 4-HOUR PERIODS = 0
PARTITION = CF13 NUMBER OF 4-HOUR PERIODS = 0
PARTITION = CF16 NUMBER OF 4-HOUR PERIODS = 0
PARTITION = SJSB NUMBER OF 4-HOUR PERIODS = 334
CONSUMED MSU 23 22 21 20
----- ----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 0.6 4.5 8.7 14.4
PARTITION = SJSD NUMBER OF 4-HOUR PERIODS = 334
CONSUMED MSU 63 62 61 60 59 58 57 56 55
----- ----- ----- ----- ----- ----- ----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 0.6 1.2 2.7 3.3 4.5 5.4 6.3 8.7 10.8
PARTITION = SJSG NUMBER OF 4-HOUR PERIODS = 0
PARTITION = SJSH NUMBER OF 4-HOUR PERIODS = 334
CONSUMED MSU 39 38 37 36 35 34 33 32 31 30
----- ----- ----- ----- ----- ----- ----- ----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 0.3 0.9 1.8 1.8 3.3 5.1 6.3 6.3 6.9 7.2
CONSUMED MSU 29
-----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 10.2
PARTITION = SYSI NUMBER OF 4-HOUR PERIODS = 0
Calculating the number of 4-hour periods
The figure below and the steps that follow provide an example of the values and the calculation that determine the value of the NUMBER OF 4-HOUR PERIODS field in the Rolling 4-Hour MSU Usage Distribution Section of the CPU Utilization Report.
BMC SOFTWARE, INC. XYZ COMPANY.
REQD 13 JUL 10 08.00.00 13 JUL 10 23.00.59 WORLDWIDE HEADQUARTERS
SHFT 00.00.00 23.59.00 DAYS=ALL
ACTL 13 JUL 10 08.09.00 13 JUL 10 23.09.00
BASED ON REC TYPE/# RECS/# SAMPLES/REC HOURS: 240-1/90/107K/15 70-1/90/107K/15
----------------------------------------- ROLLING 4-HOUR MSU USAGE DISTRIBUTION
CPU FAMILY: 2097 VERSION: 00 MODEL: 507 CEC CAPACITY = 340
PARTITION = SJSB
NUMBER OF 4-HOUR PERIODS = 67
CONSUMED MSU 238 237 236
----- ----- -----
% OF 4-HOUR PERIODS USING MORE THAN THE CONSUMED MSU 3.0 7.5 13.4
To calculate the number of 4-hour periods
- Determine the total elapsed time of the report, taken from the REC HOURS value in the BASED ON line (15 in the example).
- Determine the number of recording intervals, taken from the # RECS value in the BASED ON line (90 in the example).
- Convert the total elapsed time to minutes: 15 hours * 60 minutes per hour = 900 minutes.
- Calculate the recording interval length = 900 minutes / 90 recording intervals = 10 minutes per interval.
- Calculate the number of recording intervals per hour = 60 minutes per hour / 10 minute interval = (6) 10-minute samples per hour.
- Calculate the number of hours following the first four hours: 15 - 4 = 11.
- Calculate the number of ten-minute recording intervals in 11 hours = (11 * 6) = 66.
- Add 1, representing the last reporting interval of the first four-hour period = 66 + 1 = 67.
The total is 67 4-hour periods.
Rolling 4-Hour MSU Usage Distribution Section field descriptions
The table below describes each field in the Rolling 4-Hour MSU Usage Distribution Section of the CPU Utilization Report.
Field | Description |
---|---|
CPU FAMILY VERSION MODEL | CPU family, version, and model |
CEC CAPACITY | capacity of all CPs in millions of service units (MSUs) per hour CPs are those available for MVS partitions. |
PARTITION | partition name |
NUMBER OF 4-HOUR PERIODS | number of recording intervals that occurred in the input data after the first four hours elapsed |
CONSUMED MSU | MSUs per hour consumed by rolling four-hour periods |
% OF PERIODS USING MORE THAN THE CONSUMED MSU | percentage of rolling four-hour periods that are using more than the consumed MSU |
PROJECTED % CAPPED BY WLM | percentage of time projected to be capped by Workload Manager if the defined capacity equals the MSU amount |