HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- starting with wlm
Operating System - HP-UX
1835065
Members
2047
Online
110073
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
Forums
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
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
08-12-2002 12:57 AM
08-12-2002 12:57 AM
starting with wlm
Hi,
I want to start implementing WLM.
How do I start? What config can I define that won't disturb the users or applications in the beginning, until I can monitor them properly and understand their needs?
If I give a wide range of CPU (say min=10 and max=90), then WLM takes me down to minimum. If I give too much (min=85, max=90) then a process gets more CPU than it needs most of the time.
Can anybody give me examples of hoe they've started?
Thanks, Shelley.
I want to start implementing WLM.
How do I start? What config can I define that won't disturb the users or applications in the beginning, until I can monitor them properly and understand their needs?
If I give a wide range of CPU (say min=10 and max=90), then WLM takes me down to minimum. If I give too much (min=85, max=90) then a process gets more CPU than it needs most of the time.
Can anybody give me examples of hoe they've started?
Thanks, Shelley.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2002 01:31 AM
08-12-2002 01:31 AM
Re: starting with wlm
Hi
Use
http://www.techtarget.com/
Select hp.com
Select searchhp
Use WLM
Gives great info but you need to register
steve Steel
Use
http://www.techtarget.com/
Select hp.com
Select searchhp
Use WLM
Gives great info but you need to register
steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2002 08:52 AM
08-13-2002 08:52 AM
Re: starting with wlm
Hello Shelley,
The first thing I would suggest you do before implementing WLM is read all the documentation you can. A great source is WLM's web page at http://www.hp.com/go/wlm. It is loaded with white papers and example configurations.
To explain your situation above, from the information you gave I assume you are using the min and max keywords in an SLO structure with no goal statement. There are two types of SLOs: goal-based and entitlement-based. This is one example of an entitlement-based SLO. WLM simply grants the workload a specified amount of CPU; in this case it always gives the min. Min and max specify the range of CPU the SLO can request. However, an SLO only requests CPU when a goal (either metric or usage) is not being met. As a result, entitlement-based SLOs (which have no goal statement) do not request additional CPU for the workload.
One way to start (since I assume you have no data collectors yet to provide metrics to the SLO) is to use usage goals. Usage goal-based SLOs indicate how efficiently, within a certain range, a workload should use its CPU entitlement. The default range is 50 to 75 percent. A workload's efficiency is the amount of CPU it is using divided by its current CPU entitlement. If a workload is not consuming enough of its entitlement (or has a low efficiency), it reduces its entitlement. The opposite happens if it has a high efficiency. The entitlement is bounded by the min and max values specified in the SLO.
This and many other topics are covered in the WLM user's guide and white paper. The white paper not only gives a great overview of WLM and its concepts, but also has a section entitled "Managing application performance: quick start" which should help you get started.
The first thing I would suggest you do before implementing WLM is read all the documentation you can. A great source is WLM's web page at http://www.hp.com/go/wlm. It is loaded with white papers and example configurations.
To explain your situation above, from the information you gave I assume you are using the min and max keywords in an SLO structure with no goal statement. There are two types of SLOs: goal-based and entitlement-based. This is one example of an entitlement-based SLO. WLM simply grants the workload a specified amount of CPU; in this case it always gives the min. Min and max specify the range of CPU the SLO can request. However, an SLO only requests CPU when a goal (either metric or usage) is not being met. As a result, entitlement-based SLOs (which have no goal statement) do not request additional CPU for the workload.
One way to start (since I assume you have no data collectors yet to provide metrics to the SLO) is to use usage goals. Usage goal-based SLOs indicate how efficiently, within a certain range, a workload should use its CPU entitlement. The default range is 50 to 75 percent. A workload's efficiency is the amount of CPU it is using divided by its current CPU entitlement. If a workload is not consuming enough of its entitlement (or has a low efficiency), it reduces its entitlement. The opposite happens if it has a high efficiency. The entitlement is bounded by the min and max values specified in the SLO.
This and many other topics are covered in the WLM user's guide and white paper. The white paper not only gives a great overview of WLM and its concepts, but also has a section entitled "Managing application performance: quick start" which should help you get started.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2002 01:54 AM
08-14-2002 01:54 AM
Re: starting with wlm
Thank you for the answer, Jonathan.
I have read all kinds of documents, but am still afraid to start, so that I don't mess up the whole computer. Your idea with using the efficiency goals is a good way to start, probably, and then tune the SLOs later.
I would like to hear from anybody thtat can tell me how they've started and share some of the mistakes they've done.
Thanks, Shelley.
I have read all kinds of documents, but am still afraid to start, so that I don't mess up the whole computer. Your idea with using the efficiency goals is a good way to start, probably, and then tune the SLOs later.
I would like to hear from anybody thtat can tell me how they've started and share some of the mistakes they've done.
Thanks, Shelley.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP