Common gWLM Tasks

gWLM is a powerful tool that allows you to manage your systems in numerous ways. The sections below explain some of the more common tasks that gWLM can do for you.

Fixing the Amount of CPU a Workload Gets

gWLM allows you to give a workload a fixed amount of CPU. This fixed amount is in the form of a set amount of CPU resources given to an npar, a vpar, a virtual machine, a pset, or an fss group.

To fix the amount of CPU a workload gets, use a fixed policy provided by gWLM or create your own. Associate a fixed policy with a workload:

When creating an SRD, as described in “Getting Started with gWLM”
When adding a workload to an SRD, as described in “Adding a New Npar / Vpar / Virtual Machine / Pset / FSS Group to an SRD”
By changing the policy associated with an existing workload, as described in “Changing Which Policy is Associated with a Workload”

Resizing a Workload’s Npar, Vpar, Virtual Machine, Pset, or FSS Group as Needed

To ensure a workload gets the CPU it needs—while also allowing resource sharing when possible—gWLM provides OwnBorrow policies.

With such a policy, you indicate how much CPU a workload should own. The workload is then allocated this owned amount of CPU—when it needs it. However, you can configure the workload to:

Lend CPU resources to other workloads when it is idle
Borrow CPU resources from workloads that are idle

Associate an OwnBorrow policy with a workload:

When creating an SRD, as described in “Getting Started with gWLM”
When adding a workload to an SRD, as described in “Adding a New Npar / Vpar / Virtual Machine / Pset / FSS Group to an SRD”
By changing the policy associated with an existing workload, as described in “Changing Which Policy is Associated with a Workload”

gWLM’s utilization policies also allow resizing.

Common gWLM Tasks

Technical documentation

» Table of Contents

Fixing the Amount of CPU a Workload Gets

Resizing a Workload’s Npar, Vpar, Virtual Machine, Pset, or FSS Group as Needed