This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
AIX WLM Start and Stop is blocking activities on huge Systems
When configuring and then starting or stopping AIX WLM Workload Manager the system is not forking any new processes anymore and if it is e.g. a 5 TB AIX machine with thousands of processes it might take up to 10 minutes to start AIX Support Analysis is:
Loading / updating the WLM configuration is quite fast, but classifying processes is about 30% of the time, while classifying memory is about 70%. As all 3 of these things are done under the wlm_classes_lock, so fork will be blocked the entire time. The same is true for stopping WLM.
HACMP does not require fork for its heartbeats, but likely will need fork for its application monitors to run. Additionally Oracle forks processes from tnslsnr for each query, so will also be blocked during WLM start / stop as well. So, you are right to be concerned about starting WLM with a running workload.
It would be better if WLM could drop the wlm_classes_lock, at least periodically, during process / memory classification, so fork would be allowed at least periodically.
Do not place IBM confidential, company confidential, or personal information into any field.