gWLM cannot take advantage—even temporarily—of resources added by:

•Adjustments to entitlements for virtual machines.

•Changes to a virtual machine's number of virtual CPUs while gWLM is managing the virtual machine.

•Creation or deletion of a pset using psrset on a system where gWLM is managing pset compartments.

•Performing online cell operations using parolrad.

•Enabling and disabling Hyper-Threading.

To make use of these additional resources using the gWLM command-line interface:

1.Undeploy the SRD containing the systems that you want to adjust.

2.Make your adjustments.

3.Re-create and re-deploy the SRD.

4.Ensure policies used in the SRD do not unintentionally limit their associated workloads' resource requests.

To make use of these additional resources using the gWLM interface in System Insight Manager, follow the procedure given for that interface above.

NOTE: After manually adjusting the number of cores in an SRD, always confirm the changes after two gWLM resource allocation intervals have passed. Changes might not be as expected due to gWLM behaviors such as the ones described below.

•In an SRD with nested partitions, gWLM samples the inner partitions for their sizes before sampling the outer partitions. Adjusting resources between these samplings can cause gWLM to report incorrect sizes. If you encounter this issue, try making your adjustment again.

•In an SRD with nested partitions that includes vPars, assume you manually add cores from an unmanaged vpar. If you later remove those cores—without returning them to an unmanaged vpar before gWLM samples compartment sizes—those cores are deactivated.

Manually adjusting memory resources

The vparmodify command enables you to move memory from one vpar to another. However, gWLM cannot move CPU resources while a vparmodify operation is in progress. If a memory move takes longer than gWLM's resource allocation interval, gWLM will not be able to satisfy CPU resource requests for the missed intervals. gWLM resumes allocating resources once the memory move is complete.

You might see System Insight Manager events indicating vparmodify commands executed by gWLM are failing. The vparmodify commands fail with the following message:

A conflicting resource migration is in progress on this vPar.

Once the pending migration completes, the gWLM operation should complete.

Setting aside space for historical data

HP recommends that you allocate 4 GB of storage for every 100 workloads you will manage with gWLM. With a 5-minute sampling interval, this is enough space to store 2 years of data, which you can then use for capacity planning and performance management.

On HP-UX, the provided HP System Management Database (HPSMDB), also known as PostgreSQL, stores its data in the /var/opt/ file system. On HP-UX and Windows systems using Oracle, set aside the space in the file system used by the configured database.

34 Additional configuration and administration tasks

Page 33 Page 35
Page 34
Image 34
HP UX 11i Workload Management (gWLM/WLM) Software manual Manually adjusting memory resources
Page 33 Page 35

UX 11i Workload Management (gWLM/WLM) Software specifications

HP-UX 11i Workload Management (gWLM/WLM) software is an integral component of HP's premier UNIX operating system, designed to enhance system performance and resource management across diverse workloads. This advanced tool allows system administrators to monitor, control, and allocate resources effectively to achieve optimal performance, reliability, and service levels in enterprise environments.

One of the main features of gWLM/WLM is its ability to classify workloads and manage them according to specific policies set by the administrator. By using service level objectives (SLOs), administrators can define the performance criteria for various applications and workloads. gWLM continuously tracks these workloads, ensuring that they adhere to the defined SLOs, thus maintaining a high level of application performance.

The software employs resource pools, which segment resources such as CPU, memory, and I/O bandwidth among different workloads based on predefined priorities. This capability ensures that critical applications receive the resources they require, even during peak usage periods, thereby preventing resource starvation that could lead to system slowdowns or crashes.

Another significant characteristic of gWLM/WLM is its real-time monitoring and reporting capabilities. The software provides detailed insights into resource utilization, workload performance, and system health. Administrators can access this information through a user-friendly interface, allowing for informed decision-making and proactive management.

Integration with HP Serviceguard adds another layer of functionality, enabling high availability for critical applications. gWLM can orchestrate workload migration to ensure that service levels are maintained, even in the event of hardware failures or resource contention.

The technology behind gWLM/WLM is built on advanced algorithms that leverage historical data and predictive modeling to optimize resource allocation dynamically. This means that as workloads change, the system can automatically adjust resource distribution to meet performance targets without the need for constant manual intervention.

gWLM also supports integration with various enterprise management tools, enabling administrators to implement comprehensive monitoring and management strategies across the IT infrastructure. The scalability of gWLM allows organizations of all sizes to benefit from its robust workload management features, ensuring that they can adapt to changing demands in their operational environments.

In summary, HP-UX 11i Workload Management software offers a sophisticated solution for optimizing resource utilization, managing workloads effectively, and maintaining high performance in complex enterprise environments. Its comprehensive features and technologies make it an essential tool for any organization seeking to enhance their IT operations.
Top Page Image Contents