DLPAR and Capped and Uncapped Shared Pool Partitions

Published 02 March 2005, updated 27 April 2005

More options


Authors: Scott Vetter


This technote provides a discussion of capped and uncapped shared pool partitions with respect to DLPAR and the Advanced POWER Virtualization feature of p5 servers.


A partition that is capped and a partition that is uncapped with a weight of 0 are functionally identical. In terms of performance, you get exactly the same result (utilization can only go up to the partition's entitled capacity, not higher), but weighting can be changed from within the partition in workload-managed LPAR groups, whereas capped/uncapped state cannot. If partition capping is an area you would like to change from within a partition using workload management software in the future, an uncapped partition with a weight of 0 should be selected. The HMC is dynamically able to change a partition from capped to uncapped, and to change the weight.

Special Notices

This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.

Follow IBM Redbooks

Follow IBM Redbooks