Program guide > (deprecated) Partitioning facility > Manage the partitioning facility environment > General cluster and WPF management considerations
Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.
On demand LPAR resource advantages
If the partitioning facility (WPF) enabled applications are running within a cluster consisting of logical partition (LPAR)-capable machines, then it is possible to allocate additional central processing unit (CPU) resources to mitigate latency or higher demand scenarios without suffering even one partition subset outage. AIX and pSeries offers this support, and, for many customers this approach could be critical.
For example, if you are using a blade center or Linux cluster, for example (many smaller footprint servers), and want to even out the load against the given cluster members, an outage for at least a subset of the endpoint partitions will occur. This outage occurs because the partitioning facility's ability to balance partitions dynamically between blades, either in mass or by selectively moving one partition at a time between application servers. However, this does result in a short term outage as the partition being moved needs to be taken offline (deactivated with a PartitionUnLoadEvent(...)) and then reactivated on another physical blade.
In the case of an LPAR capable machine, more resources can be provided to handle partitions that are receiving abnormally high number of transaction requests. Many of the IBM servers now allow administrators to actually contact the IBM Web site to purchase additional LPAR resources when heavy load situations occur.
Parent topic:General cluster and WPF management considerations
General cluster and WPF management considerations