Table of Contents
Advertisement
v For LPs without processor resource capping, PR/SM LPAR enforces the
v If a logical CP falls outside the enforceable ranges for logical CPs entitled to less
v Unused CP cycles to which a logical CP is entitled are made available to other
v An uncapped coupling facility LP with shared CPs and coupling facility channels
Processing Weight Management Examples
For the formulas used in the following two examples, see "Processing Weight
Management Formulas" on page 3-41.
Example 1. With Processor Resource Capping: In the following example:
v Six physical CPs are online
v All LPs are capped
v All LPs have sufficient workload demand to use their shares
Table 3-3. PR/SM LPAR Processor Weight Management with Processor Resource Capping
LCPs
LP
Online
Weight (1)
A
6
B
3
C(2)
3
C(3)
Total Capacity of the
Shared PCP
1000 / 6 PCPs = 166.7 = PCP capacity
Resources
Legend:
LCP
Logical CP
PCP
Physical CP
Notes:
1. Use the Customize/Delete Activation Profiles task available from the CPC Operational Customization tasks list to
open a reset or image profile to set the processing weight for an LP. The Processing weight field is located on the
Processor page for the LP.
2. The logical CPs for LP C (2) fall outside the enforceable range because each logical CP's share is only 4% of a
physical CP.
3. The LP's range is bounded by the line shown for LP C (3). Typically, though, even this configuration will see
results comparable to the line shown for LP C (2).
3-40
PR/SM Planning Guide
1/10 or more of one physical CP. Typically, PR/SM LPAR will manage processing
weights to within 1% of the LP's physical CP share. See "Example 1. With
Processor Resource Capping."
processing weights to within 3.6% of the LP's physical CP share for logical CPs
entitled to 1/2 or more of one physical CP. Typically, PR/SM LPAR will manage
the processing weights to within 1% of the LP's physical CP share. See
"Example 2. Without Processor Resource Capping" on page 3-41.
than 1/10 of a physical CP using capping or less than 1/2 of a physical CP not
using capping, PR/SM LPAR enforces the processing weights to within 3.6% of
the total capacity of the shared physical CP resources. However, PR/SM LPAR
should typically manage the processing weights to within 1% accuracy.
logical CPs in proportion to the weights set for the other logical CPs.
defined honors its processing weight up to a point. PR/SM LPAR attempts to help
ensure that each logical CP defined to a coupling facility LP gets at least 1 run
time interval of service per every 100 milliseconds. For example, for a typical
12.5 millisecond run time interval, each logical CP gets 1/8th of a physical CP.
Weight per
LCP %
LCP
of PCP
500
83.3
480
160.0
20
6.7
3.6%
3.6%
Share
Total
50
3.0
–
96
5.8
–
4
0.2
–
12
Resulting
Resulting
Utilization
Weight Range
Range
80.3–86.3
48.2%–51.8%
154.2–165.3
46.3%–49.7%
6.5–6.9
2.0%– 2.1%
0.0–18.7
0.0%– 5.6%
Advertisement
Chapters
Table of Contents
