- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: WLM vs PRM
Operating System - HP-UX
1752285
Members
4984
Online
108786
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2001 07:30 AM
03-02-2001 07:30 AM
WLM vs PRM
If i assume i'm not using Goals Based SLOs.
If WLM is only a modifier of the prmconf, how can we define priorities if WLM acts only when CPU usage is 100% (prm fonctionnality without capping).
Regards
If WLM is only a modifier of the prmconf, how can we define priorities if WLM acts only when CPU usage is 100% (prm fonctionnality without capping).
Regards
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2001 02:16 PM
03-05-2001 02:16 PM
Re: WLM vs PRM
The PRM configuration that WLM generates always has PRM CPU capping enabled. By doing so, WLM will always be able to control the amount of CPU given to each workload. With no goals defined, the WLM configuration can simply be viewed as a PRM configuration with fixed CPU caps.
In the absence of performance goals, WLM can still prioritize workloads on a system.
You can create service level objectives (SLOs) with a CPU usage goal. These goals do not require external metrics and will try to give a workload more CPU when it is busy and less when it is idle.
You can also use the weight keyword to indicate the relative importance of each workload, then turn on the distribute_excess tunable to have WLM equitably share the CPU cycles amoung the workloads.
In the absence of performance goals, WLM can still prioritize workloads on a system.
You can create service level objectives (SLOs) with a CPU usage goal. These goals do not require external metrics and will try to give a workload more CPU when it is busy and less when it is idle.
You can also use the weight keyword to indicate the relative importance of each workload, then turn on the distribute_excess tunable to have WLM equitably share the CPU cycles amoung the workloads.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP