gWLM addresses priority levels from highest to lowest, allocating
resources to all requests at a given priority level before considering
lower priority requests. If, at some priority level, all requests
cannot be satisfied, the remaining resources are distributed so
that the total resource allocation for each workload is as near
the proportion of its weight relative to the sum of all the weights
as possible.If gWLM has satisfied all resource requests at all priorities
and there are resources still to be allocated, it will distribute
the remaining resources by weight. Again, this is so that the total resource
allocation for each workload is as near the proportion of its weight
relative to the sum of all the weights as possible.
Table 1-1 “Default weights by policy type” lists the default
weights for the various policy types. For policies with weights,
you can also set the weight explicitly.
Table 1-1 Default weights by policy type
Policy type | Default weight |
|---|
Fixed | N/A
(You cannot deploy an SRD where
all the workloads with fixed policies are not satisfied.) |
| Utilization | 1 |
| OwnBorrow | Equal to its owned CPU resources |
| Custom | 1 |
 |
| |
|
 | NOTE: To ensure CPU allocations behave as expected for OwnBorrow
policies, the sum of the CPU resources owned cannot exceed the number
of CPUs in the SRD. (However, if the sum is less than the number
of CPUs in the SRD, the excess is distributed to all compartments
in proportion to the amounts owned. Thus, workloads will routinely
get more than they are due.) |
|
| |
|
Printable version
