I am looking at some basic workload management control and monitoring issues on a DB2 pureScale setup. Is there anything unique or different about WLM on pureScale? How does it work?
An interesting albeit rare scenario that we have seen occur when using CPU limits in a shared LPAR which resulted in a downward “death spiral” with the hypervisor continuosly reducing the amount of CPU available to DB2 and severely affecting DB2 performance.
Avoid problematic WLM configurations by learning about how the WLM dispatcher determines if a service class is active or not!
What should happen on your system when both service classes are not executing work or when one or the other does not need its full complement of allocated CPU?
Find out more about hard and soft CPU shares offered by the WLM dispatcher.
The Workload Manager dispatcher technology introduced in DB2 10.1 offers a powerful and simple interface for controlling CPU. The two controls used to provide direction to the WLM dispatcher are CPU limits and CPU shares. Ever wonder how to choose between them?