|
A workload is a collection of applications whose performance is to be
managed as a single unit. You can base a workload on an npar, a vpar, a
pset, or an fss group. gWLM then manages resource allocation for the npar,
vpar, pset, or fss group.
The Workloads tab allows you to:
The Workloads tab
provides a table that includes the following columns:
* Applies only to workloads based on psets or fss groups
Re-sort the rows by selecting the column heading that you would
like to sort by.
 | | Create a new workload |
This section applies only to workloads based on psets
or fss groups. To create workloads based on npars or vpars, use the
Manage Workloads wizard. To create a new workload:
Select the following menu item if you have not already done so:
Optimize
Global Workload Manager (gWLM)
Edit Workloads
Select the [New] button.
Scroll down to see the new section "New Workload."
Enter a name for the new workload. Legal characters for the name
are A-Z, a-z, 0-9, the dash character ( - ), the period ( . ), and the
underscore character ( _ ); the first character must be a letter.
(Optional) Indicate the applications and user processes to
go in the workload. You can place processes in a workload using one or more of the
following methods: The following steps explain how to set up these records. For
precedence rules and additional information, see the section
Tips for managing psets and fss groups
below.
Specify one or more user names for which processes will be
automatically moved into this workload.
Enter the name of a user whose processes should run in the
workload.
Select the [>>] button to move an
entry from the User Name field
to the User List.
Repeat the previous two steps for additional users as
desired.
(Optional)
Specify one or more applications to automatically move into the
workload.
To add an application to the
workload: Select the Applications tab. Select the [New] button. Scroll down to see the new fields.
Enter the full path, starting with /, to the application in the
Application Pathname field.
You can use wildcards ([,
], ?,
and *)
to specify the filename, but not
the directory name.
For a script that uses a shell or interpreter, specify the full
path to the shell/interpreter being used
in the script in this field. Then, be sure to specify an entry in the
Alternate Name field, discussed in the
next step.
Enter, in the Alternate
Name field, any alternate names the application takes when
running, if you want to place the application in separate workloads
based on its alternate names. You can use pattern matching notation to
designate a group of similarly named processes.
For a script that uses a shell or interpreter, enter the name of the
script or interpreter--excluding its path.
Alternate names should match the first
non-shell item in the COMMAND column (that is, the command name with no
options) of the output from the ps -ef command.
Alternate names are common for complex programs such as database
programs that launch many processes and rename them.
Select the [>>] button to move an
entry from the Alternate Name field
to the Alternate Name List.
Repeat the previous two steps for additional alternate
names as desired.
Select the [OK] button to add the application.
Add more applications to the workload if desired. As you add applications, they are listed in the table at the top
of the Applications tab.
Select the [OK] button to the right of the
Workload Name
field to finish defining the new workload.
|
Tips for managing psets and fss groups This section presents various items to be aware of when managing
workloads based on psets or fss groups. Placement of process trees
gWLM's application records and user records move only the indicated process
to a workload. To move an entire process tree, use
gwlmplace --recurse.
Precedence of placement techniques
As mentioned above, you can place processes in workloads with user records,
application records, and the gwlmplace command. gWLM
checks that
processes are in their appropriate workloads every 30 seconds,
based on the following rules of precedence.
For each process:
Has the process been placed using the gwlmplace
command? Yes: Leave process where it is No: Continue to next step If you use gwlmplace --recurse to move a process
tree, all processes in the tree are considered to have been placed using
gwlmplace.
Is there a matching application record? Yes: Then assign the process to that workload No: Continue to next step Is there a matching user record? Yes: Then assign the process to that workload No: Continue to next step Is the parent of the process assigned to a workload? Yes: Then inherit the parent's workload No: Continue to next step
Place nonroot processes in the default workload.
(gWLM leaves root processes where they are.)
Management of short-lived processes
gWLM polls the system every 30 seconds to determine whether
processes are running in their assigned workloads. Consequently, you should
not assign short-lived processes to workloads.
Use of the default pset or default fss group
If you let processes run in the default pset or the default fss group, they
will be competing against all the other processes that are not explicitly
placed in workloads. To ensure appropriate resource allocations for your
processes, place them in workloads by specifying user records or
application records when defining workloads or by using the
gwlmplace command.
| | Edit a workload |
To edit a workload:
Select the following menu item if you have not already done so:
Optimize
Global Workload Manager (gWLM)
Edit Workloads
Select the workload you want to edit.
Select the [Edit] button.
Scroll down to see the new section "Edit Workload."
Make edits in the Applications tab and
Users tab
(applies only to workloads that are based on psets or fss groups).
For information on these tabs, see the
Applications tab description or
the Users tab description above.
Select the [OK] button to the right of the
Workload Name
field to finish editing the workload.
| | Delete a workload |
To delete workloads:
Select the following menu item if you have not already done so:
Optimize
Global Workload Manager (gWLM)
Edit Workloads
Select one or more workloads to delete.
Select the [Delete] button.
Confirm the deletion.
Error message: Cannot delete workload because it is in an SRD If you see the above error message when attempting to delete a
workload, your next steps depend on whether the workload's SRD is
deployed or undeployed, as explained below.
To delete a workload in an undeployed SRD:
Select the menu item:
Optimize
Global Workload Manager (gWLM)
Edit SRDs
Complete the steps to perform one of the following three options:
Delete the SRD and its workloads Delete the SRD (without deleting its workloads) Then, return to the
Edit Workloads window to delete the
workload
Deploy the SRD then continue with the steps below for a deployed SRD
For information on completing any of these options, see the
online help for the Edit SRDs
window.
To delete a workload in a deployed SRD:
Use the gWLM menu item
Unmanage Workloads to remove the
workload from its SRD
Return to the Edit Workloads window to
delete the workload
|
