Overview of dynamic MSU limit
Parameter | Description |
---|---|
Initial MSULIMIT | Initial starting MSU limit |
Max MSULIMIT | Maximum number of allowable MSUs to be consumed collectively by all LPARs and capacity groups that the policy or subpolicy manages |
Inc MSULIMIT | Number of MSUs by which the initial MSU limit incrementally increases if iCap is unable to run low importance workloads |
Adj MSULIMIT | Percentage of low importance work at which iCap starts to increase the MSU limit |
Scope | Designates the LPARs whose low-importance work is considered when calculating the low-importance workload percentage to determine if iCap needs to increase MSU limit. |
For more information, see Policy-level-and-subpolicy-level-parameters.
How a dynamic MSU limit works
After you set the required parameters for a policy or subpolicy, iCap uses the following process to run a dynamic MSU limit.
- At startup, the master PAS uses your initial MSU limit (lowest value) or the monthly MSU limit.
For more information about the monthly MSU limit, see Step 3. iCap begins to increase the MSU limit when at least one LPAR or capacity group is capped, the MSU limit is approaching, and one of the following conditions exists:
- The policy or subpolicy cannot run low importance work.
- The policy's or subpolicy's percentage of low importance work decreases to less than your specified Adj MSULIMIT value for LPARs with priority less than or equal to SCOPE parameter.
When the master PAS has an IPL, iCap saves the peak MSU limit (also called the monthly MSU limit) in the registry.
iCap uses the monthly MSU limit the next time the master PAS starts.
iCap resets the monthly MSU limit to the initial MSU limit at midnight on the second day of the month.