PowerVM Dynamic Platform Optimizer and PowerVP

© 2013 IBM Corporation

PowerVMDynamic Platform Optimizer and PowerVP

Tracy Smith and Steve NasypanyOct. 22 (4:15-5:30) and 24 (10:30-11:45) 2013


Dynamic Platform Optimizer and PowerVP

During an IPL of the entire Power System, the Hypervisor determines an optimal resource placement strategy for the server based on the partition configuration and the hardware topology of the system.

Partition placement can become sub-optimal because of:–Dynamic creation and deletion of partitions–DLPAR operations that add and remove processors or memory–After LPAR has been running, ending the LPAR and restarting with

processor or memory configuration changes –Hibernation (Suspend or Resume)–LPM – Live Partition Mobility–CHARM – CEC Hot add, Repair, & Maintenance

(This is a Node operation)

Why Dynamic Platform Optimizer - DPO

2



DPO is a PowerVM virtualization feature that enables users to improve partition memory and processor placement (affinity) on Power Servers after they are up and running.

DPO performs a sequence of memory and processor relocations to transform the existing server layout to the optimal layout based on the server topology.

Client Benefits–Ability to run without a platform IPL (entire system)–Improved performance in a cloud or highly virtualized environments–Dynamically adjust topology after mobility

What is Dynamic Platform Optimizer - DPO

3



Dynamic Platform Optimizer

Partition XMemory

Partition YMemory

Partition ZMemory

Free LMBs

Legend

Partition YProcessors

Partition XProcessors Partition Z

Processors

SystemAdministratorruns DPO analysis toget current orcalculated score

After up and running partitions came become

spread across multiple nodes

4



Dynamic Platform Optimizer

Partition XMemory

Partition YMemory

Partition ZMemory

Free LMBs

Legend


Partition XProcessors Partition Z

Processors

Partition XProcessors


Partition ZProcessors

SystemAdministratorruns DPO affinityoptimizer

5



Introduced in fall 2012 (with feature code EB33) • 770-MMD and 780-MHD with firmware level 760.00• 795-FHB with firmware level 760.10 (760 with fix pack 1)• Recommend 760_069 has enhancements below

Additional systems added spring 2013 with firmware level 770– 710,720,730,740 D-models with firmware level 770.00– 750,760 D-models with firmware level 770.10 (770 with fix pack 1)– 770-MMC and 780-MHC with firmware level 770.20 (770 with fix pack 2)– Performance enhancements – DPO memory movement time reduced– Scoring algorithm improvements – Recommend firmware at 770_021

Future plans – Affinity scoring at the LPAR level with firmware level 780 • 770-MMB, 780-MHB (4Q2013)• 795-FHB (4Q2013)• 770-MMD, 780-MHD (2014)

DPO – Supported Hardware and Firmware levels

* Some Power models and firmware releases listed above are currently planned for the future and have not yet been announced. * All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

6


Dynamic Platform Optimizer and PowerVPPOWER7 Firmware Release Levels by ServerPower Server MTMs GA1 GA2 GA3 GA4 GA6 GA7 GA8

710 720 730 740 760 770 780

795 9119-FHB n/a GA S n/a S 760.10 n/a S

775 9125-F2C n/a n/a GA 7.3.1 n/a n/a n/a n/a

770/780 9117-MMB; 9179-MHB GA 7.1.1 S S n/a n/a n/a S 780.0011/22/13

770/780 9117-MMC; 9179-MHCAdded IOC

n/a n/a n/a GA n/a S 770.2006/07/13

n/a

770/780 9117-MMD; 9179-MHDIOC added p7+

n/a n/a n/a n/a GA n/a Planned 2Q2014

760 9109-RMD n/a n/a n/a n/a n/a GA 770.1003/15/13

n/a

710/730 8231-E2B n/a GA S n/a n/a n/a n/a

7R2Linux

8246-L2B(iListed RPQ - Never Announced)

n/a n/a GA n/a n/a n/a n/a

710/730 8231-E1C; 8231-E2C n/a n/a n/a GA n/a n/a n/a

7R1/7R2Linux

8246-L1C; 8246-L1S8246-L2C; 8246-L2S

n/a n/a n/a GA 740.40 n/a n/a n/a

710/730 8231-E1D; 8231-E2D n/a n/a n/a n/a n/a GA 770.0002/20/13

n/a

7R1/7R2Linux

8246-L1D; 8246-L1T8246-L2D; 8246-L2T

n/a n/a n/a n/a n/a GA 770.0002/20/13

n/a

720/740 Analytics

8202-E4B; 8205-E6B8492-DW2; 8493-SV2

n/a GA S n/a n/a n/a n/a

720/740 Analytics

8202-E4C; 8205-E6C8492-DW3; 8493-SV3

n/a n/a n/a GA n/a n/a n/a

720/740 8202-E4D; 8205-E6D n/a n/a n/a n/a n/a GA 770.0002/20/13

n/a

750/755HPC 8233-E8B; 8236-E8C GA 7.1.0 n/a S n/a n/a n/a n/a

750 8408-E8D n/a n/a n/a n/a n/a GA 770.1003/15/13

n/a

7R4Linux

8248-L4T n/a n/a n/a n/a n/a GA 770.2108/07/13

n/a

HM

C &

Firmw

are combinations

Pow

er System

code matrix

7



Power 780-MHD Properties screen

8



More free blocks make it easier and faster More non-relocatable blocks make it tougher

- Guarded-out LMBs, TCEs, multi-partition PLIC heaps, etc. At least one free memory block required

- Hypervisor can use unlicensed (Non activated) memory for the purpose of relocation

Enterprise systems support CUoD– PoD – Processor on Demand– MoD – Memory on Demand

Solution Similar to Solving a Tile Puzzle

Power Systems Capacity on Demand: http://www-03.ibm.com/systems/power/hardware/cod/index.html

9



HMC view of free memory blocks (System properties)

10



User Interface

Control is via HMC command-line interface Can connect remote to HMC via PUTTY

11



Select an Operation with (V7R7.8.0) HMC firmware

■ Select: System/Server name – Operations – Scheduled Operations

12



User Interface update with (V7R7.8.00) HMC firmware

HMC scheduled Operations Options → New... Creating a scheduled Operation

13



Select an Operation with (V7R7.8.0) HMC firmware

■ Select: Monitor/Perform Dynamic Platform Optimize

■ (Note: Will only be available on DPO capable systems)

14



Setup Schedule Operation: Date & Time / Repeatwith (V7R7.8.0) HMC firmware

Configure Normal Schedule Operation Parameters:

15



Schedule Operations: DPO Options / Target and Triggerswith (V7R7.8.0) HMC firmware

Information

■ System Name

■ Potential Affinity Score – The estimated maximum score after running DPO

■ Current Affinity Score – The current score

■ Affinity Thresholds – default 00

■ Server Affinity Threshold [0-100] – If this value is greater than the Current Affinity Score

■ Server Affinity Delta Threshold [0-99] – If this value is less than the Potential minus the Current Score

System affinity scoreNot LPAR affinity score

16



Configure Management Console Notificationswith (V7R7.8.0) HMC firmware

■ Setup Email Notify Alert

■ Enable email notifications

17



DPO OptionsDPO Analysis

– Systems that support 760 and later firmware – Generates a current and predicted system affinity score– Score is from 0 to 100 (100 be best)– Analysis uses a very small amount of CPU

Systems that support 780 firmware – More granular affinity scoring – Current and predicted affinity score for active partitions – Better able to analysis business critical partitions

Start and Stop of affinity optimization– Controls for starting and stopping an operation– Sets of partitions can be prioritized or protected (excluded)

Affinity optimization status – Shows progress percentage if currently running– Result (success, failure, etc.) of last operation – Impacted partitions

18



Implementation Details – Work Flow

DetermineLPAR priority

Compute preliminary optimization plan

Recomputeoptimization plan

Reassign CPUsto LPARs

HMC PHYP

Optimize HPTsin LPAR priority order

Optimize partition memoryin LPAR priority order

CLI “optmem” request

Hardware Page Tables (HPT)objects require contiguous LMBs.Some HPT objects may not be moved to desired location due to fragmentationcaused by guarded memory, TCE tables, etc.

Same high-level flow for optimization andscore prediction. No LMBs or CPUs actually moved for prediction. Predictedscore based on predicted virtual memory/CPUlayout.

Based on new memory layout.

One LMB at a time. Atomic units (relocation granules) are 512K.

Notify affected LPAR OSes

Asynchronous notification to HMC when complete.HMC retrieves status/score with separate command.

19



Current and Predicted Affinity scores prior to 780 firmware

# lsmemopt –m managed_system –o currscore# lsmemopt –m managed_system –o calcscore

[--id request_partition_list][--xid protect_partition_list]

• Currscore computes the current system-wide affinity score (0-100)

• Calcscore computes the predicted system-wide score that would likely result from running a DPO operation (includes optional parms just like the actual DPO operation)

currscore

calcscore

20



Current and Predicted Affinity enhancement with 780 firmware

Scores at the partition level along with the system wide scores

lsmemopt –m managed_system –o currscore –r [sys | lpar]

lsmemopt –m managed_system –o calcscore –r [sys | lpar][--id request_partition_list][--xid protect_partition_list]

sys = system-wide score (default if the –r option not specified)lpar = partition scores

21



22



lpar_name=tbvio1_Production,lpar_id=1,curr_lpar_score=100,predicted_lpar_score=100lpar_name=tbvio2_Production,lpar_id=2,curr_lpar_score=100,predicted_lpar_score=100lpar_name=ce154_vios_ceisen,lpar_id=3,curr_lpar_score=100,predicted_lpar_score=100

lpar_name=EisenTest,lpar_id=4,curr_lpar_score=100,predicted_lpar_score=100lpar_name=tbvio3_esp,lpar_id=5,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=demo5_ceisen,lpar_id=6,curr_lpar_score=100,predicted_lpar_score=100lpar_name=hyper,lpar_id=7,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-vio_davidson,lpar_id=8,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-nim_davidson,lpar_id=9,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-ca1_davidson,lpar_id=10,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-ca2_davidson,lpar_id=11,curr_lpar_score=100,predicted_lpar_score=10 0lpar_name=isd190nim,lpar_id=12,curr_lpar_score=100,predicted_lpar_score=100lpar_name=isd189_pittman,lpar_id=13,curr_lpar_score=100,predicted_lpar_score=100lpar_name=bmnode1,lpar_id=14,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-ca3_davidson,lpar_id=15,curr_lpar_score=100,predicted_lpar_score=100lpar_name=sc-ca4_davidson,lpar_id=16,curr_lpar_score=100,predicted_lpar_score=100

tasmith@tbhmc1:~> lsmemopt -m Turbo -o calcscore -r lpar Example 1: 780 firmware current affinity score at the LPAR level

23



Example 2: 780 firmware current affinity score at the LPAR level

# lsmemopt –m calvin –o currscore –r lparlpar_name=calvinp1,lpar_id=1,curr_lpar_score=100lpar_name=calvinp2,lpar_id=2,curr_lpar_score=100lpar_name=calvinp50,lpar_id=50,curr_lpar_score=100lpar_name=calvinp51,lpar_id=51,curr_lpar_score=nonelpar_name=calvinp52,lpar_id=52,curr_lpar_score=100lpar_name=calvinp53,lpar_id=53,curr_lpar_score=74lpar_name=calvinp54,lpar_id=54,curr_lpar_score=nonelpar_name=calvinp55,lpar_id=55,curr_lpar_score=nonelpar_name=calvinp56,lpar_id=56,curr_lpar_score=100lpar_name=calvinp57,lpar_id=57,curr_lpar_score=nonelpar_name=calvinp58,lpar_id=58,curr_lpar_score=nonelpar_name=calvinp59,lpar_id=59,curr_lpar_score=nonelpar_name=calvinp60,lpar_id=60,curr_lpar_score=nonelpar_name=calvinp61,lpar_id=61,curr_lpar_score=none# lsmemopt -m calvin -o currscore -r sys curr_sys_score=97

24



Example 3: 780 firmware predicted affinity score

# lsmemopt –m calvin –o calcscore –r lparlpar_name=calvinp1,lpar_id=1,curr_lpar_score=100,predicted_lpar_score=100lpar_name=calvinp2,lpar_id=2,curr_lpar_score=100,predicted_lpar_score=100lpar_name=calvinp50,lpar_id=50,curr_lpar_score=100,predicted_lpar_score=100lpar_name=calvinp51,lpar_id=51,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp52,lpar_id=52,curr_lpar_score=100,predicted_lpar_score=100lpar_name=calvinp53,lpar_id=53,curr_lpar_score=74,predicted_lpar_score=100lpar_name=calvinp54,lpar_id=54,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp55,lpar_id=55,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp56,lpar_id=56,curr_lpar_score=100,predicted_lpar_score=100lpar_name=calvinp57,lpar_id=57,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp58,lpar_id=58,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp59,lpar_id=59,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp60,lpar_id=60,curr_lpar_score=none,predicted_lpar_score=nonelpar_name=calvinp61,lpar_id=61,curr_lpar_score=none,predicted_lpar_score=none# lsmemopt -m calvin -o calcscore -r sys curr_sys_score=97,predicted_sys_score=100,requested_lpar_ids=none,protected_lpar_ids=none

25



HMC CLI: Starting/Stopping a DPO Operation

optmem –m managed_system –t affinity –o start [--id requested_partition_list][--xid protect_partition_list]

– Partition lists are comma-separated and can include ranges– Include –-id 1,3, 5-8 – Requested partitions: partitions that should be prioritized (default = all LPARs)– Protected partitions: partitions that should not be touched (default = no LPARs)– Exclude by name –x CAB, ZIN or by LPAR id number --xid 5,10,16-20

optmem –m managed_system –t affinity –o stop

Use these switchesto exclude partitionsby name or number

example:Partitions that are not DPO aware

26



HMC CLI: DPO Status

# lsmemopt –m managed_system

in_progress=0,status=Finished,type=affinity,opt_id=1,progress=100,requested_lpar_ids=none,protected_lpar_ids=none,“impacted_lpar_ids=106,110”

• Unique optimization identifier

• Estimated progress %

• LPARs that were impacted by the optimization (i.e. had CPUs, memory, or their hardware page table moved)

27



Example of HMC CLI Commands

# lssyscfg -r sys -F namezg23aezg24he

# lsmemopt -m zg24he -o currscorecurr_sys_score=84

# lsmemopt -m zg24he -o calcscorecurr_sys_score=84,predicted_sys_score=86,"requested_lpar_ids=1,2,17,105,106,107,108,109,110,111",protected_lpar_ids=none

# optmem -m zg24he -t affinity -o start

# lsmemopt -m zg24hein_progress=0,status=Finished,type=affinity,opt_id=2,progress=0,requested_lpar_ids=none,protected_lpar_ids=none,”impacted_lpar_ids=106,110”

# lsmemopt -m zg24he -o currscorecurr_sys_score=86

28



PHYP Implementation Details Optimization Priority Order

– Primarily based on user-configured affinity group ID (255-1).– Otherwise, based on CPU/memory resources (more = higher priority)– Higher priority partitions get best placement– Higher priority partitions get out of Virtual Page Table (VPT) mode earlier

Hardware Page Tables (HPTs)– Require contiguous LMBs– May necessitate some defragmentation– HPT relocation dependent on # of free LMBs on system

CPU Reassignment– Fast operation – not dependent on optimization priority

Partition LMB moves– Planned in partition priority order– Higher priority partitions finish earlier and immediately taken out of “VPT” mode– Can be long-running operation (more on this later)

Impacted partitions notified at the end of DPO operation– Partitions can re-fetch affinity properties in response to notification

29



While DPO is Running Hypervisor leverages underlying technology developed for CHARM to relocate

memory and virtual CPUs– Relocation transparent to partitions– There will be some amount of degraded performance while the impacted

partitions memory is being relocated due to virtual page table (VPT) mode.

Majority of DPO time spent moving LMBs (HPTs and LPAR memory)– Depends on:

• CPU workload• # of LMBs that require relocation• System configuration

CPU Cycles– LMB relocation performed in multiple threads.– PHYP dispatcher finds idle cycles, “steals” cycles periodically to perform work

in the background.– Cycles not stolen from protected partitions.

30



Running DPO

DPO aware Operating Systems – AIX: 6.1 TL8 or later, AIX 7.1 TL2 or later – IBM i: 7.1 TR6 or later– Linux: Some reaffinitization in RHEL7/SLES12.

(Fully implemented in follow-on releases)– VIOS 2.2.2.0 or later– HMC V7R7.6.1

Partitions that are DPO aware are notified after DPO completesReaffinitization Required

– Performance team measurements show reaffinitization is critical– For older OS levels, users can exclude those partitions from optimization, or

reboot them after running the DPO Optimizer

Affinity (at a high level) is as good as CEC IPL– (assuming unconstrained DPO)

Call support for latest fixes

31



DPO Impact on Example Bank with (AIX 61TL5)This is a worse case on a non DPO aware LPAR

The following DPO result is based on 4node 780-MHD with latest efw7.6, Friendly bank workload running on AIX 61J (TL5)

21% better than scrambled affinity.

DPO Performance Progress

17% worse than scrambled affinity.

600

700

800

900

1000

1100

1200

IPL scrambledaffinity

partiallyenable DPO

DPO enabledwith no reboot

of LPARs

DPO enabledand reboot all

LPARs

txn/

s

worse than scrambled affinity.

BASELINE Scrambled DPO in DPO PartitionGood Placement Affinity Progress Complete Re-booted

Slide courtesy of AIX Performance Team

32



More Information

IBM PowerVM Virtualization Managing and Monitoring (June 2013)– SG24-7590-04: http://www.redbooks.ibm.com/abstracts/sg247590.html?Open

IBM PowerVM Virtualization Introduction and Configuration (June 2013)– SG24-7940-05: http://www.redbooks.ibm.com/abstracts/sg247940.html?Open

POWER7 Information Center under logical partitioning topiccs– http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=%2Fp7hat%2Fiphblm

anagedlparp6.htm IBM DeveloperWorks

– https://www.ibm.com/developerworks/community/blogs/PowerFW/entry/dynamic_platform_optimizer5?lang=en

POWER7 Logical Partitions “Under the Hood” – http://www-

03.ibm.com/systems/resources/power_software_i_perfmgmt_processor_lpar.pdf

33



PowerVP

34



Setting the stage:– Performance analysts requesting more detailed and

comprehensive tools, especially with POWER7– Current tools present partition views– Need a single tool to view system-wide performance

across entire CEC with ability to drill down to all individual partitions

Developed as an internal tool – Rapid development of prototype technology– Tie together new POWER7 internal tools– Developed working prototype, tried use cases

Very high interest from:– Power Systems performance analysts– Technology previews at AIX TCC & IBM i LUG

Background

35



During an IPL of the entire Power System, the Hypervisor determines an optimal resource placement strategy for the server based on the partition configuration and the hardware topology of the system.

There was a desire to have a visual understanding of how the hardware resources were assigned and being consumed by the various partitions that were running on the platform.

It was also desired to have a visual indication showing a resource’s consumption and when it was going past a warning threshold (yellow) and when it was entering an overcommitted threshold (red.)

Why PowerVP - Power Virtualization Performance

36



PowerVP

o

SystemTopology

Node Drill Down

PartitionDrill Down

37



Overview Graphically displays data from existing and new performance tools Converges performance data from across the system Shows CEC and partition level performance data Illustrates topology utilization with colored “heat” threshold settings Enables drill down for both physical and logical approaches Allows real-time monitoring for immediate drill down Logs data for later analysis and comparison Simplifies physical/virtual environment, monitoring, and analysis

38



• We can see each node has four chips/sockets. We can also see numbers in the boxes which indicate how busy each of the chips are. The green lines between the nodes shows the traffic on the SMP fabric between each node.

PowerVP – System Topology

• The initial view shows the hardware topology of the system you are logged into.

• In this view, we see a Power 795 with all eight books and/or nodes installed.

39



• We can also see the green lines showing the busses between the chips. We can also see the memory controllers and the GX busses which shows traffic to and from our remote I/O. We also see green lines on the top, bottom, and corners. This is the SMP connections to other nodes and shows traffic.

PowerVP – Node drill down

• This view appears when you click on one of the nodes and allows you to see the resources being consumed by the workload running on the system. In this view we can see this system is using eight core chips.

40



• We can drill down on several of thee resources. Example: I can drill down on the Disk transfer rate to see how balanced my I/Ops are across the drives assigned to this LPAR.

PowerVP - Partition drill down

• The view allows us to drill down on resources being used by a specific partition that we clicked on.

• In this view, we see CPU, Memory, Disk Iops, and Ethernet being consumed. We can also get an idea of cache and memory affinity.

41



Power Hardware

FW/Hypervisor

Operating system

Applications

Monitor

Client device that is

capable of supporting Java Swing

IBM i, Linux, AIX or VIOS

Thread PMUs

(partition level)

Core HPMCs(CEC level)

Chip PMUlets(CEC level)

Partition collector

System collector

Hypervisor interfaces

system interfaces

Requires fw 7.7 or later

System-wide collector One required per system P7 topology information P7 chip/core utilizations P7 Power bus utilizations memory and I/O utilization LPAR entitlements, utilization

Partition collectors Required for logical view LPAR CPU utilization

CPI analysis Cache analysis

Collectors

42



Power System models and ITE’s with 770 firmware support• 710-E1D, 720-E4D, 730-E2D, 740-E6D (also includes Linux D models)• 750-E8D, 760-RMD• 770-MMC, 780-MHC• p260-22X, p260-23X, p460-42X, p460-43X, p270-24X, p470-44X, p24L-7FL• 71R-L1S, 71R-L1C, 71R-L1D, 71R-L1T, 7R2-L2C, 7R2-L2S, 7R2-L2D, 7R2-L2T

Power System models with 780 firmware support (future plans)– 770-MMB, 780-MHB, and 795-FHB (4Q2013)– 770-MMD, 780-MHD (2014)

PowerVP supported Power models and ITE’s

* Some Power models and firmware releases listed above are currently planned for the future and have not yet been announced.* All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All models with pre-770 firmware do not have the required new instrumentation to support PowerVP

43



Current plans– Announce and GA in 4Q 2013– Available via:

• Standalone product• Or as part of PowerVM Enterprise Edition

– Dependent on 7.7 or later firmware • Select POWER7 and POWER7+ models supported

(see previous chart for details)– Agents will run on IBM i, AIX, Linux on Power and VIOS

• i 7.1, AIX 6.1 and 7.1, Linux (RHEL 7 64 bit, others?)

Future plans– Support for new hardware– Integration with other performance tools and advisors– Add additional metrics

Product Plans

44



System Topology View – Single entry point for CEC wide Monitoring

45



Node drill-down view – Virtual/Physical Topology UtilizationHardware resources of LPARs are highlighted in the Node view

46



POWER7+ 770/780 Four Socket Planner Memory Layout

47

Loc Code Conn Ref

Power 770/780 D Technical Overview


Dynamic Platform Optimizer and PowerVP IBM Confidential

DEMO

48



Thank you

49



Power 750/760 D Technical Overview

POWER7+ Four Socket Planer 750/760 Layout

50



This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in other countries, and the information is subject to change without notice. Consult your local IBM business contact for information on the IBM

offerings available in your area.Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions

on the capabilities of non-IBM products should be addressed to the suppliers of those products.IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give

you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA.

All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or guarantees either expressed or implied.

All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the results that may be achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations

and conditions.IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions

worldwide to qualified commercial and government clients. Rates are based on a client's credit rating, financing terms, offering type, equipment type and options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal

without notice.IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies.

All prices shown are IBM's United States suggested list prices and are subject to change without notice; reseller prices may vary.IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this

document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally-available systems. Some measurements quoted in this document may have been estimated through extrapolation. Users of this document

should verify the applicable data for their specific environment.

Revised September 26, 2006

Special notices

51



IBM, the IBM logo, ibm.com AIX, AIX (logo), AIX 5L, AIX 6 (logo), AS/400, BladeCenter, Blue Gene, ClusterProven, DB2, ESCON, i5/OS, i5/OS (logo), IBM Business Partner (logo), IntelliStation, LoadLeveler, Lotus, Lotus Notes, Notes, Operating System/400, OS/400, PartnerLink, PartnerWorld, PowerPC, pSeries, Rational, RISC

System/6000, RS/6000, THINK, Tivoli, Tivoli (logo), Tivoli Management Environment, WebSphere, xSeries, z/OS, zSeries, Active Memory, Balanced Warehouse, CacheFlow, Cool Blue, IBM Systems Director VMControl, pureScale, TurboCore, Chiphopper, Cloudscape, DB2 Universal Database, DS4000, DS6000, DS8000,

EnergyScale, Enterprise Workload Manager, General Parallel File System, , GPFS, HACMP, HACMP/6000, HASM, IBM Systems Director Active Energy Manager, iSeries, Micro-Partitioning, POWER, PowerExecutive, PowerVM, PowerVM (logo), PowerHA, Power Architecture, Power Everywhere, Power Family, POWER Hypervisor, Power Systems, Power Systems (logo), Power Systems Software, Power Systems Software (logo), POWER2, POWER3, POWER4, POWER4+, POWER5, POWER5+, POWER6, POWER6+, POWER7, System i, System p, System p5, System Storage, System z, TME 10, Workload Partitions Manager and X-Architecture are trademarks

or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at

the time this information was published. Such trademarks may also be registered or common law trademarks in other countries.

A full list of U.S. trademarks owned by IBM may be found at: http://www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

AltiVec is a trademark of Freescale Semiconductor, Inc.AMD Opteron is a trademark of Advanced Micro Devices, Inc.

InfiniBand, InfiniBand Trade Association and the InfiniBand design marks are trademarks and/or service marks of the InfiniBand Trade Association. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered

trademarks of Intel Corporation or its subsidiaries in the United States and other countries.IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries or both.Microsoft, Windows and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries or both.

NetBench is a registered trademark of Ziff Davis Media in the United States, other countries or both.SPECint, SPECfp, SPECjbb, SPECweb, SPECjAppServer, SPEC OMP, SPECviewperf, SPECapc, SPEChpc, SPECjvm, SPECmail, SPECimap and SPECsfs are

trademarks of the Standard Performance Evaluation Corp (SPEC).The Power Architecture and Power.org wordmarks and the Power and Power.org logos and related marks are trademarks and service marks licensed by Power.org.

TPC-C and TPC-H are trademarks of the Transaction Performance Processing Council (TPPC).UNIX is a registered trademark of The Open Group in the United States, other countries or both.

Other company, product and service names may be trademarks or service marks of others.Revised December 2, 2010

Special notices (cont.)

52



The IBM benchmarks results shown herein were derived using particular, well configured, development-level and generally-available computer systems. Buyers should consult other sources of information to evaluate the performance of systems they are considering buying and should consider conducting application oriented testing. For additional information about the benchmarks, values and systems tested, contact your local IBM office or IBM authorized reseller or access the Web site of the benchmark

consortium or benchmark vendor.

IBM benchmark results can be found in the IBM Power Systems Performance Report at http://www.ibm.com/systems/p/hardware/system_perf.html .

All performance measurements were made with AIX or AIX 5L operating systems unless otherwise indicated to have used Linux. For new and upgraded systems, the latest versions of AIX were used. All other systems used previous versions of AIX. The SPEC CPU2006, LINPACK, and Technical Computing benchmarks were compiled using

IBM's high performance C, C++, and FORTRAN compilers for AIX 5L and Linux. For new and upgraded systems, the latest versions of these compilers were used: XL C for AIX v11.1, XL C/C++ for AIX v11.1, XL FORTRAN for AIX v13.1, XL C/C++ for Linux v11.1, and XL FORTRAN for Linux v13.1.

For a definition/explanation of each benchmark and the full list of detailed results, visit the Web site of the benchmark consortium or benchmark vendor.

TPC http://www.tpc.orgSPEC http://www.spec.org

LINPACK http://www.netlib.org/benchmark/performance.pdfPro/E http://www.proe.com

GPC http://www.spec.org/gpcVolanoMark http://www.volano.com

STREAM http://www.cs.virginia.edu/stream/SAP http://www.sap.com/benchmark/

Oracle, Siebel, PeopleSoft http://www.oracle.com/apps_benchmark/Baan http://www.ssaglobal.com

Fluent http://www.fluent.com/software/fluent/index.htmTOP500 Supercomputers http://www.top500.org/

Ideas International http://www.ideasinternational.com/benchmark/bench.htmlStorage Performance Council http://www.storageperformance.org/results

Revised December 2, 2010

Notes on benchmarks and values

53

PowerVM Dynamic Platform Optimizer and PowerVP

Documents

Transcript of PowerVM Dynamic Platform Optimizer and PowerVP