HP Matrix Operating Environment Software - Manual (Page 93)

Available utilization metrics
The following types of utilization metrics are shown on the Visualization View and Workload
View:
• CPU utilization Percentage of total CPU resources in use. For a complex, virtual partition
server, enclosure, VC domain, VC domain group, or Serviceguard cluster compartment, the
aggregate CPU utilization is calculated as the average utilization of its subcompartments.
CPU meters shown in compartments that do not have CPUs are an aggregation.
• Memory utilization Percentage of total memory resources in use, and on the Visualization
tab total memory in GB (defined as 2
30
bits). The memory utilization shown for an entire
system is not the same as the sum of the memory utilization of all of the workloads it contains.
In the data for the entire system, this metric includes dynamic buffer cache and system
memory that is not directly attributable to any specific process and therefore is not included
in any workload.
For a complex, virtual partition server, enclosure, VC domain, VC domain group, or
Serviceguard cluster compartment, the aggregate memory utilization is calculated as the
average utilization of its subcompartments. Memory meters shown in compartments that
do not have memory are an aggregation.
• Network I/O Network throughput (transmitted plus received), in one of Kb/s (10
3
bits per
second) Mb/s (10
6
bits per second) Gb/s (10
9
bits per second). Current utilization determines
the units to be used. On managed systems running HP-UX or Microsoft Windows, the
maximum length of the Network I/O meter is calibrated to a theoretical maximum based
on the network interface type. On Windows managed systems where data is collected by
way of the Agentless Data Collector or on Linux managed systems, the maximum is calibrated
to a “high-water mark” (the highest value seen on this system so far) that is tracked by the
Utilization Provider. For VMM, the maximum is first retrieved from the setting obtained
from Configure
→Edit Network and Disk I/O Capacity…. If the maximum is not set there,
the last 5 hours worth of VMM data is used to calculate a high-water mark.
For a complex, virtual partition server, enclosure, VC domain, VC domain group, or
Serviceguard cluster compartment, the aggregate network I/O utilization is calculated as
sum of the utilization of its subcompartments. Note that Network I/O meters shown in
compartments that do not have network I/O are an aggregation.
• Disk I/O Disk I/O throughput (stored plus retrieved), in one of KB/s (10
3
bits per second)
MB/s (10
6
bits per second) GB/s (10
9
bits per second). Current utilization determines the
units to be used. The maximum length of the disk I/O meter is calibrated to a high-water
mark (the highest value seen on this system so far) that is tracked by the Utilization Provider.
For VMM, the maximum is first retrieved from the setting obtained from Configure
→Edit
Network and Disk I/O Capacity… . If the maximum is not set there, the last 5 hours worth
of VMM data is used to calculate a highwater mark.
For a complex, virtual partition server, enclosure, VC domain, VC domain group, or
Serviceguard cluster compartment, the aggregate disk I/O utilization is calculated as sum
of the utilization of its subcompartments. Disk I/O meters shown in compartments that do
not have disk I/O are an aggregation.
• Power The power meter shows the power utilization of a compartment in Watts (where
supported), based on calibration information designated from Configure
→Calibrate Power
(All Selected Systems)... or alternatively, from the Calibrate Power link in the meter
callout. When CPU utilization data is available, power meters are provided for any physical
server, including standalone servers, nPartitions, or server blades. Power meters typically
display a warning triangle until a power calibration has been performed for a system. Once
calibrated using either of the above methods, the power meter value can be displayed.
Reviewing real-time utilization data 93