HP Matrix Operating Environment Software - Manual (Page 123)

Table A-2 Define static estimates — settings to guide Estimated Utilization assumptions for
workload
Description Attribute or action Area
Fractional or whole number of cores assumed to be
used by the new workload on the assigned system.
Default: 0.0 CPU Core Utilization Static Profile
Memory assumed to be used by the new workload.
Default: 0.0 Memory Utilization (GB)
Network bandwidth assumed to be used by the new
workload. Default: 0.0 Network I/O Utilization (Mb/s)
Disk bandwidth assumed to be used by the new
workload. Default: 0.0 Disk I/O Utilization (MB/s)
Clicking this button automatically fills in the following
values from the Assigned System selection:
• System Model – Model number for simulated
system. Default: None
• Hardware Processor Family – Processor name.
Default: Itanium
• CPU Core Count – Total number of cores on the
simulated system. Default: 0
• CPU Speed (GHz) Typical speed of the selected
processor. Default: 0.0
These fields can also be filled in manually using values
that you choose for the workload.
Import from Assigned System
TIP:
Providing estimates for a static profile The baseline that you enter should represent your best
guess as to the load the particular application or workload will place on the system where you
assign it. For example, if you have an application that you plan to assign to a 4-core system, and
it typically uses two cores, you would enter 2.0 for CPU utilization. In the same way, you would
enter a processor speed based on the system the workload originally ran on, and the amount of
memory usually consumed by the workload on its previous system.
Once you have a baseline workload that represents current behavior, you can create additional
workloads with different values to experiment with variations in CPU speed, available memory,
and variable utilization limits to discover the behavior and performance of the workload in
different scenarios.
Adjusting for virtualization changes
Capacity Advisor gives you the ability to provide compensating factors to help Capacity Advisor
adjust needed resources when analyzing moving workloads from a physical system to a virtual
machine on a VM host or from a virtual machine to a physical system.
(For information on how utilization is calculated for each resource, see
Appendix C (page 149) .)
CPU Virtualization Overhead %
The following section presents the scaling factor that you can use to more accurately simulate
the impact of changing a standalone system to a virtual machine, or a virtual machine into a
standalone system. In these situations, CPU utilization can increase or decrease due to the
overhead required for the virtual machine software. The CPU Virtualization Overhead % helps
you to account for this in a scenario.
Adjusting for virtualization changes 123