HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- WLM runaway
Operating System - HP-UX
1836715
Members
2843
Online
110108
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
06-09-2006 03:44 AM
06-09-2006 03:44 AM
WLM runaway
Has anyone experience a Work Load Manager runaway scenario ?
Scenario:
1 RP7420 divided equally into 2 vPars using WLM to manage just the CPU allocations according to workload.
WLM executed a CPU reallocation to on server (A).
Upon review here are a couple notes:
1) The CPU utilization reported by glance, sar, top and MWA never showed an increase in CPU utilzation ( consistantly showed about 40% ).
2) WLM reports by wlminfo slo -l shows currently over 600 share requests hence the reallocation. WLM is still reporting 600+ share requests even though the system CPU utilization is not showing the workload.
I have a call into HP but the current review is simply that I am out of date on a single patch out of many.
All attempts to recreate this scenario where WLM will not release it's assumed workload metric have failed. Test show the product works as advertised.
Looking to see if anyone has experienced the same.
Thanks in advance.
Tim
Scenario:
1 RP7420 divided equally into 2 vPars using WLM to manage just the CPU allocations according to workload.
WLM executed a CPU reallocation to on server (A).
Upon review here are a couple notes:
1) The CPU utilization reported by glance, sar, top and MWA never showed an increase in CPU utilzation ( consistantly showed about 40% ).
2) WLM reports by wlminfo slo -l shows currently over 600 share requests hence the reallocation. WLM is still reporting 600+ share requests even though the system CPU utilization is not showing the workload.
I have a call into HP but the current review is simply that I am out of date on a single patch out of many.
All attempts to recreate this scenario where WLM will not release it's assumed workload metric have failed. Test show the product works as advertised.
Looking to see if anyone has experienced the same.
Thanks in advance.
Tim
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2006 08:45 AM
06-20-2006 08:45 AM
Re: WLM runaway
Solution:
The WLM usage goal uses %IDLE which in most cases is 100-%SYS-%USER-%WIO. In a specific test I only had a backup running which generated little if no CPU but reported a lot of %WIO as it should. But, why would I want WLM to allocate another CPU for an IO load ? Not me.
I configured WLM to use the glance metric for CPU_TOTAL_UTIL. Now WLM only reallocates CPU when there is a CPU load, not an IO load.
SLO looks like this.
slo servera_slo {
pri = 1; # Change this value
mincpu = 2;
maxcpu = 12800;
#goal = usage _CPU;
goal = metric avg_glance_cpu < 75;
}
tune avg_glance_cpu {
coll_argv = wlmrcvdc glance_gbl GBL_CPU_TOTAL_UTIL ;
}
This is another terrible case of generic performance monitors using %WIO in CPU load calculations.
Hope this information is usefull to others in the future.
The WLM usage goal uses %IDLE which in most cases is 100-%SYS-%USER-%WIO. In a specific test I only had a backup running which generated little if no CPU but reported a lot of %WIO as it should. But, why would I want WLM to allocate another CPU for an IO load ? Not me.
I configured WLM to use the glance metric for CPU_TOTAL_UTIL. Now WLM only reallocates CPU when there is a CPU load, not an IO load.
SLO looks like this.
slo servera_slo {
pri = 1; # Change this value
mincpu = 2;
maxcpu = 12800;
#goal = usage _CPU;
goal = metric avg_glance_cpu < 75;
}
tune avg_glance_cpu {
coll_argv = wlmrcvdc glance_gbl GBL_CPU_TOTAL_UTIL ;
}
This is another terrible case of generic performance monitors using %WIO in CPU load calculations.
Hope this information is usefull to others in the future.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 09:39 AM
06-21-2006 09:39 AM
Re: WLM runaway
One last piece of information:
Identified a patch after more searching ( PHSS_34270 WLM Cumulative ). There is a specific fix for this issue.
1) WLM is not calculating usage correctly for strictly host-based configurations
Either soloution mentioned in this thread will work.
Identified a patch after more searching ( PHSS_34270 WLM Cumulative ). There is a specific fix for this issue.
1) WLM is not calculating usage correctly for strictly host-based configurations
Either soloution mentioned in this thread will work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2006 05:26 AM
07-12-2006 05:26 AM
Re: WLM runaway
can I give myself points :)
See previous details for solutions.
See previous details for solutions.
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