View Historical Reports

The amount of a resource, such as CPU, that gWLM set aside for a compartment after arbitrating resource requests from the policies for all the compartments.

In managed mode, gWLM makes an allocation available to a compartment. In advisory mode, however, gWLM simply reports what the allocation would be--without actually affecting resource allocations on a system.

The amount of a resource a compartment actually had.

For CPU, size may differ from the allocation when gWLM is deployed in advisory mode.

The minimum amount of a resource that a compartment could have had. As an example, with the CPU resource, CompartmentMin is the number of CPUs a compartment could have had based on how it was defined when created using npar, vpar, or pset commands.

gWLM's discovery feature evaluated the system to determine this value.

The maximum amount of a resource that a compartment could have had. For example, with the CPU resource, CompartmentMax is the number of CPUs a compartment could have had based on how it was defined when created using npar, vpar, or pset commands.

gWLM's discovery feature evaluated the system to determine this value.

The amount of a resource that was consumed by the processes in a compartment.

For instance, with the CPU resource, compartment consumption is the amount of CPU that was used by the compartment's processes.

The percentage resulting from dividing a workload's consumption by its allocation.

For example, assume a workload had an allocation of 5 CPUs. If the workload consumed 4.5 CPUs, its utilization percentage would have been 4.5/5, or 90%.

The amount of a system resource that a policy asked gWLM to give to the policy's compartment. (Parameters you specified in defining a policy would have restricted its request.)

The amount of a resource, such as CPU, that gWLM set aside for a compartment after arbitrating resource requests from the policies for all the compartments.

In managed mode, gWLM makes an allocation available to a compartment. In advisory mode, however, gWLM simply reports what the allocation would be--without actually affecting resource allocations on a system.

The amount that was allocated may have been restricted by the minimum and maximum number of CPUs you specified for compartments when creating them using npar, vpar, or pset commands.

The amount of a resource a compartment actually had.

For CPU, size may differ from the allocation when gWLM is deployed in advisory mode.

The amount of owned CPU resources. This item appears only when graphing OwnBorrow policies.

PolicyMin is the minimum amount of a resource, such as number of CPUs, that a policy would have requested for any compartment with which it was associated. Effective PolicyMin is the larger of PolicyMin and CompartmentMin (the minimum amount of a resource that a compartment could have had).

PolicyMax is the maximum amount of a resource, such as number of CPUs, that a policy would have requested for any compartment with which it was associated. Effective PolicyMax is the smaller of PolicyMax and CompartmentMax (the maximum amount of a resource that a compartment could have had).

The value of a metric that was used in a policy. gWLM calculates utilization metrics for you.

The size of a compartment in CPUs.

The value of the metric that was used in a custom policy.

The value that drove a policy, influencing its resource requests to gWLM.

For a target CPU utilization, gWLM attempts to keep a workload's CPU utilization below the target by adding CPU resources when the workload is using too much of its current CPU allocation. For example, assume a workload has a utilization policy with a target of 80% and a size of 5 CPUs. If the workload is consuming 4.5 CPUs, its utilization percentage is 4.5/5, or 90%. gWLM would attempt to allocate additional CPU resources to the workload to meet the target. A size of 6 CPUs would result in a utilization percentage of 4.5/6, or 75%, meeting the target.

A target can also be a value the workload should stay above, such as x transactions per second. Adding resources in this case helps the workload maintain the number of transactions.

The desired size, in CPUs, of the workload. This value drove a policy, influencing its resource requests to gWLM.

The value the metric (graphed as 'Reading') was being compared against. This value drove a policy, influencing its resource requests to gWLM.

The amount of a system resource that a policy asked gWLM to give to the policy's compartment. (Parameters you specified in defining a policy restricted its request.)