HP-UX Workload Manager User's Guide

NOTE With Hyper-Threading disabled, each core is seen as a CPU. With

Hyper-Threading enabled, each core can be seen as multiple, logical

CPUs.

•The wlminfo par and wlminfo host commands now explicitly

display core statistics, such as in the following display for the

wlminfo par command:

Hostname Intended Cores Cores Cores Used Interval

• The wlminfo group command now displays memory utilization of all

groups in the current deployed configuration. In addition, this

command now supports the -v option to display each group’s

gmincpu, gmaxcpu, gminmem, and gmaxmem values, if they are

available in the current deployed configuration. This new option is

ignored if live data is not being displayed (for example, when the -o

option is being used). If memory management is not being used, a

dash (-) instead of a zero is displayed in the ‘Mem Shares’ column. If

a group’s gmincpu, gmaxcpu, gminmem, or gmaxmem value is not

assigned in the current configuration, a dash (-) is displayed in the

corresponding column.

For more information, see wlminfo(1M) or “Monitoring WLM with

the wlminfo command” on page 343.

• WLM supports the use of Extended Regular Expressions (EREs) for

defining alternate names for application records. This support

requires that PRM C.03.02 or later is running on the same system.

For more information, see “Assigning applications to workload

groups (optional)” on page 166 and “Pattern matching for renamed

application processes” on page 457.

• WLM supports placement of processes and assignment of user access

based on Unix groups. You can assign Unix groups to workload

groups by defining the uxgrp record in the prm structure. Processes

whose effective group ID (GID) matches a Unix group record will run

in the associated workload group. WLM supports Unix group records

only if PRM C.03.02 or later is running on the system. For more

information, see “Assigning Unix groups to workload groups

(optional)” on page 165.