Mspp Aix Vug

7/26/2019 Mspp Aix Vug

http://slidepdf.com/reader/full/mspp-aix-vug 1/41

© 2011 IBM Corporation

Shared Processor Pools

James Nash

[email protected]




Trademarks

The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

The following are trademarks or registered trademarks of other companies.

* All other products may be trademarks or registered trademarks of their respective companies.

Notes:

Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user willexperience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actualenvironmental costs and performance characteristics will vary depending on individual customer configurations and conditions.

This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change withoutnotice. Consult your local IBM business contact for information on the product or services available in your area.

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

Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance,compatibili ty, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

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.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license there from.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

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.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA,WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is notactively marketed or is not significant within its relevant market.

Those trademarks followed by ® are registered t rademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

2



© 2011 IBM Corporation3




Agenda

• Processor Terminology− Physical

− Virtual

− Logical

• Capped/Uncapped and Weight

• Shared Processor Pools

• Multiple Shared Processor Pools

• Creating Additional Pools• Monitoring Pools

4




LPAR LPAR LPAR

Deconfigured

Inactive (CoD)

Logical (SMT)

Physical

(Installed)

Virtual

Dedicated

Shared

Processor Terminology Concepts




Define Processor Requirements

How much CPU wi ll this LPAR

have at boot time?

How much could we consumefrom the shared pool?

When would the LPAR be able

to fully consume all 4 virtual

processors?

What values can be changed

dynamically?

6


http://slidepdf.com/reader/full/mspp-aix-vug 7/41© 2011 IBM Corporation

Virtual Processors in Shared Processor Pool

Virtual processors represent concurrent operating system operations

Entitled Capacity (physical CPU) is spread across these virtual

processors

Optimal number of virtual processors depends on the workload

– Number of threads – What threads are doing

Number of virtual processors (Minimum and Desired) is obtained by: – Rounding entitled capacity to next whole number

– Example

• Minimum = 0.50 (entitlement) -> 1 virtual processor minimum

• Desired = 2.25 (entitlement) -> 3 virtual processors desired Maximum number of virtual processors is 10x entitlement

– Do you want maximum 0.8 entitled over 8 virtual processors?

– Some art, experimentation warranted

– Some workloads need more concurrence, some need fewer and more

powerful virtual processors



Virtual Processor Recommendations

If you have more virtual processors than CPUs in the pool

– You may have greater context switching – You may have greater overhead.

If you have too few virtual processors too small

– You limit the processing capacity of an uncapped partition

– Cannot use more than 1.0 physical CPU cycles thru 1 virtual processor

Example partition with desired 0.5 CPU units and excess capacity

– With 1 virtual processor the partition cannot exceed 1.00 physical

CPUs

– With 2 virtual processors the partition could use up to 2.00 physical

CPUs

– With 5 virtual processors (max) physical capacity can reach 5.00• Maximum %ent is 1000% (0.1 entitled capacity, on 1 virtual processor,

uncapped)



Capped Shared Processor LPAR

Maximum Processor Capacity

Entitled Processor CapacityProcessor

Capacity

UtilizationLPAR Capacity Utilization

Pool Idle Capacity Available

Time

minimum processor capacity

ceded capacity

utilized capacity

9



Uncapped Shared Processor LPAR

Maximum Processor Capacity

Processor

Capacity

Utilization

Pool Idle Capacity Available

Time

Entitled Processor Capacity

minimum processor capacity

Utilized Capacity

ceded capacity

10



Shared Processor Pool

LPAR

#1

LPAR

#2

SPLPAR

#3

SPLPAR

#4

SPLPAR

#5

SPLPAR

#6

SPLPAR

#7

SPLPAR

#8

Hypervisor

Pool 0

Core Core Core CoreCoreCoreCoreCoreCoreCore CoreCore

1 Core

(dedicated)

2 Cores

(dedicated)

Physical

Learning point: All activated, non-dedicated cores are automatically used to create the shared processor

pool. The shared processor pool size will can change as dedicated LPARs are started /

stopped.

Shared Processor Pool (SPLPARs) are based on Micro-Partitioning technology

11



Shared Dedicated Processors

Once an lpar is defined as “dedicated”, profile must be edited to modify the

“Processor Sharing” attributes

“Allow when partition is inactive” – Set

by default, allows processor sharing

when partition is shutdown.

“Allow when partition is active” – allows

Sharing when the partition is active and

CPU cycles are unused.

12



Utilizing Unused Dedicated Processor Capacity

0

25

50

75

100

125

150

175

200

1-way Dedicated Wasted Dedicated 0.5 Uncapped 1 0.5 Uncapped 2

0

25

50

75

100

125

150

175

200

1-way Dedicated Wasted Dedicated 0.5 Uncapped 1 0.5 Uncapped 2

Donation option enabled, a dedicated partition donates its excess cycles to the

uncapped partitions.

Result: Better System Utilization

2 partitionsUncapped

Evenly weighted

1 partition

2-way server with:

Two evenly weighted 1-way uncapped partitions ( 100% Utilized )

1-way dedicated partition ( Variable workload )

Unused processor cycles in dedicated partition are wasted

13



virtual CPU

splpar 2

virtual CPU

splpar1

Dispatch

Wheel (10ms)

Dispatched

virtual timebase

virtual timebase

virtual timebase

virtual timebase

virtual CPU

splpar 1virtual timebase

virtual CPU

splpar 4

virtual timebase

virtual CPU

splpar 3virtual timebase

100 units

physical CPU

timebase

Shared Processor Partitions

Shared processor conceptsPartitions run on virtual processors

running only part of the time on

physical processors

Minimum "size" of a partition is1/10th of a processor

Partition physical capacity is called

entitlement, or entitled capacity

and defined as a number of

physical processing units. each unit is 1/100th of a processor

14



What weight?

Answer 1:LPAR1 gets all needed free

resources because of the

higher weight.

Answer 2:

LPAR1 gets 2 of the free

CPUs and LPAR2 gets 1.

Answer 3:

LPAR1 gets 2/3rd of the free CPUs

and LPAR2 gets 1/3rd.

3 CPU

LPAR1

Weight 40

LPAR2

Weight 20

3 CPU3 CPU

Units Available

15



Multiple Shared Processor Pools

SPLPAR

Appl

Server

SPLPAR

Web

Server

SPLAR

DB.

SPLPAR

Appl

Server

SPLPAR

Web

Server

Shared Processor Pool

SPLPAR

Appl

Server

SPLPAR

Web

Server

SPLPAR

DB.

SPLPAR

Appl

Server

SPLPAR

Web

Server

Pool-1 Pool-3Pool-0

Limit processor resources to a group of SPLPARs

Up to 64 Processor Pools per server

Can help with software licensing

Help balance Prod/Dev on the same server

POWER5 POWER6

16



Configuring MSPPs

1. Select Configuration

2. Shared Processor Pool

Management

17




DefaultPool (Pool ID 0)

18




DefaultPool (AKA SPP0)

The default Shared-Processor Pool has the same attributes as

a user-defined Shared-Processor Pool except that theseattributes are not directly under the control of the system

administrator—they have fixed values.

Shared-Processor Pool ID is always 0

Always named “defaultpool” AKA “defaultpool(0)”

Maximum pool capacity is all the processors currently residing

in the physical shared processor pool.

– Active physical processor cores less any dedicated processors

Reserved Processor Capacity is zero

Entitled pool capacity is the sum of the Entitled Capacities for

the partitions residing in the default shared processor pool

19




Configuring MSPPs cont’d1. Select Shared Processor

Pool

20

1. Enter Pool Name

2. Set Reserved Processing Units

3. Set Maximum Processing Units




Terminology

Maximum Pool Capacity (user-defined)

Each Shared-Processor Pool has a maximum capacity associated with it. The Maximum

Pool Capacity defines the upper boundary of the processor capacity that can be utilized by

the set of micro-partitions in the Shared-Processor Pool. The Maximum Pool Capacity must

be represented by a whole number of processor units.

Entitled Pool Capacity

Associated with a Shared-Processor Pool is an Entitled Pool Capacity. The Entitled Pool

Capacity of a Shared-Processor Pool defines the guaranteed processor capacity that is

available to the group of micro-partitions in the Shared processor Pool. The Entitled Pool

Capacity is the sum of the entitlement capacities of the micro-partitions in the Shared-

Processor Pool plus the Reserved Pool Capacity.

Reserved Pool Capacity (user-defined)The Reserved Pool Capacity is in addition to the processor capacity entitlements of the

individual micro-partitions in the Shared-Processor Pool. The Reserved Pool Capacity is

distributed amongst uncapped micro-partitions in the Shared-Processor Pool according to

their uncapped weighting. The default value for the Reserved Pool Capacity is zero (0).

21




Multiple Shared Processor Pool Attr ibutes

Pool ID

range 0 thru 63 “Pool ID 0” is the default shared pool (SPP0)

• Cannot be modified The pool name can be up to 14 characters long and can contain blanks

Maximum Pool Capacity Defines the upper boundary of the processor capacity that can be utilized bythe set of micro-partitions in the Shared-Processor Pool. The Maximum PoolCapacity must be represented by a whole number of processor units.

Reserved Pool Capacity

In addition to the processor capacity entitlements of the individual micro-partitions in the Shared-Processor Pool. The Reserved Pool Capacity isdistributed amongst uncapped micro-partitions in the Shared-Processor Poolaccording to their uncapped weighting. The default value for the Reserved PoolCapacity is zero (0).

The pool attributes and partition assignments can be changed dynamicallywhile the micro-partitions are running.

22




A New Shared Processor Pool is Created




Adding Partitions to a Shared Pool1. Select Partitions

3. Select Pool Name

24

2. Select Partition name




Partitions using our new pool










Two Levels of processor capacity resolution

Level0 The first level, Level0, is the resolution of capacity within the same

Shared-Processor Pool. Unused processor cycles from within a

Shared-Processor Pool are harvested and then redistributed to any

eligible micro-partition within the same Shared-Processor Pool.

Level1

When all Level0 capacity has been resolved within the Multiple Shared-

Processor Pools, the POWER Hypervisor harvests unused processor

cycles and redistributes them to eligible micro-partitions regardless of

the Multiple Shared-Processor Pools structure. This is the second level

of processor capacity resolution.




Level0 vs Level1

29




Multiple Shared Processor Pools

LPAR

#1

SMT=On

LPAR

#2

SMT=Off

SPLPAR

#3

SMT=On

SPLPAR

#4

SMT=Off

SPLPAR

#5

SMT=On

SPLPAR

#6

SMT=On

SPLPAR

#7

SMT=On

SPLPAR

#8

SMT=On

Hypervisor

Pool

# 0

Pool MaxPU = 3

#1 ReservedPU = 0.5

Pool MaxPU = 4

#2 ReservedPU = 0.6

Weight = 255

PU = 1.2

V

L

V

L L L

Capped

PU = 0.5

V

Weight = 30

PU = 1.5

V

L

V

L

Weight = 10

PU = 0.1

V

L L

Weight = 100

PU = 1.2

V V

Weight = 100

PU = 1.2

V

L

V

L L L

V

L L L L

L L

Core Core Core CoreCoreCoreCoreCoreCoreCore CoreCore

L L L L

1 Core

(dedicated)

2 Cores

(dedicated)

Virtual

Logical

Physical

Physical

MaxPU … A Whole number, specifies maximum processing un its that can be

consumed by all of the SPLPARs running in this pool,

ReservedPU = Addit ional, guaranteed Processing Units for each pool (could be 0)

Default Pool ID = 0 (cannot specify MaxPU or ReservedPU for the Default Pool)

30



IBM System p


Changes to vmstat (pc and ec)

# vmstat 2 4

Syst em conf i gur at i on: l cpu=4 mem=512MB ent =0. 30

(With both LPARs running)

kt hr memory page f aul t s cpu- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

r b avm f r e r e pi po f r sr cy i n sy cs us sy i d wa pc ec

2 0 117516 2638 0 0 0 0 0 0 7 249437 410698 11 53 36 0 0. 88 292. 6

2 0 117516 2638 0 0 0 0 0 0 23 249638 413057 11 53 36 0 0. 93 308. 53 0 117516 2638 0 0 0 0 0 0 10 250452 417638 11 53 36 0 0. 91 303. 1

3 0 117516 2638 0 0 0 0 0 0 9 254519 420552 11 53 36 0 0. 88 293. 2

(With ONE LPAR running)

r b avm f r e r e pi po f r sr cy i n sy cs us sy i d wa pc ec

3 0 117516 2634 0 0 0 0 0 0 7 149274 237336 12 64 24 0 1. 71 569. 32 0 117516 2634 0 0 0 0 0 0 10 152628 249000 12 63 25 0 1. 72 573. 52 0 117516 2634 0 0 0 0 0 0 9 157462 252112 12 63 25 0 1. 72 573. 0

2 0 117516 2634 0 0 0 0 0 0 9 152194 250861 12 62 26 0 1. 70 567. 4

lcpu and ent are new

pc – physical capacity ec - % entitled capacity



IBM System p


Changes to iostat (pc and ec)

# iostat 2 4

Syst em conf i gur at i on: l cpu=4 dr i ves=2 ent =0. 30 paths=2 vdi sks=2

t t y: t i n t out avg- cpu: % user % sys % i dl e % i owai t physc % ent c

0. 0 32. 6 12. 3 62. 2 25. 5 0. 1 0. 9 289. 6

Di sks: % t m_act Kbps t ps Kb_r ead Kb_wr t n

hdi sk0 0. 0 1. 9 0. 5 4 0

hdi sk1 0. 0 0. 0 0. 0 0 0

physc – physical capacity

entc - % entitled capacity

lcpu, ent, vdisks are new



IBM System p


lsdev, bindprocessor, sar and logical CPUs

# lsdev -Cc processor

pr oc0 Avai l abl e 00- 00 Pr ocessorpr oc2 Avai l abl e 00- 02 Pr ocessor

Physical (virtual) CPUs

Logical (SMT) CPUs

Logical (SMT) CPUs

# bindprocessor -q The avai l abl e pr ocessor s ar e: 0 1 2 3

# sar -P ALL 2 2

AI X sys02_ai x1 3 5 00C07F5F4C00 08/ 03/ 07

Syst em conf i gur at i on: l cpu=4 ent =0. 30

15: 09: 47 cpu %usr %sys %wi o %i dl e physc %entc

15: 09: 49 0 13 64 0 23 0. 20 67. 3

1 11 52 0 37 0. 14 48. 3

2 14 71 0 15 0. 28 94. 3

3 12 57 0 31 0. 25 82. 8

- 13 62 0 25 0. 88 292. 7



IBM System p


Changes to topas (Physc and %Entc)

# topas

Topas Moni t or f or host : sys15_ni m1 EVENTS/ QUEUES FI LE/ TTYMon Oct 24 15: 32: 23 2011 I nter val : 2 Cswi t ch 195. 3K Readch 0Syscal l 107. 3K Wr i t ech 4341

Ker nel 48. 6 | ############## | Reads 0 Rawi n 0User 10. 2 | #### | Wr i t es 2 Tt yout 140Wai t 0. 0 | | For ks 0 I get s 0I dl e 41. 2 | ############ | Execs 0 Namei 3Physc = 0. 86 %Ent c= 285. 6 Runqueue 2. 6 Di r bl k 0

Wai t queue 0. 0

Net wor k KBPS I - Pack O- Pack KB- I n KB- Out MEMORY Tot al 1. 0 18. 4 0. 0 1. 0 0. 0 PAGI NG Real , MB 512

Faul t s 0 % Comp 92. 2Di sk Busy% KBPS TPS KB- Read KB- Wr i t Steal s 0 % Noncomp 6. 6 Tot al 0. 0 0. 0 0. 0 0. 0 0. 0 PgspI n 0 % Cl i ent 6. 6

PgspOut 0Fi l eSyst em KBPS TPS KB- Read KB- Wr i t PageI n 0 PAGI NG SPACE Tot al 0. 0 0. 0 0. 0 0. 0 PageOut 0 Si ze, MB 512

Si os 0 % Used 0. 0Name PI D CPU% PgSp Owner % Fr ee 100. 0l oadgen 299170 17. 7 0. 4 r oot NFS ( cal l s/ sec)t opas 253952 0. 0 1. 5 r oot Ser V2 0 WPAR Act i v 0nf sd 303254 0. 0 0. 2 r oot Cl i V2 0 WPAR Tot al 0gi l 65568 0. 0 0. 1 r oot Ser V3 0 Press: "h"- hel p j ava 229532 0. 0 46. 2 pconsol e Cl i V3 0 "q"- qui t



IBM System p


topas –L flag# topas -L

I nt er val : 2 Logi cal Par t i t i on: sys15_ni m1 Mon Oct 22 15: 33: 05 2007Psi ze: 2 Shared SMT ON Onl i ne Memory: 512. 0Ent : 0. 30 Mode: UnCapped Onl i ne Logi cal CPUs: 4Par t i t i on CPU Ut i l i zat i on Onl i ne Vi r t ual CPUs: 2%usr %sys %wai t %i dl e physc %entc %l busy app vcsw phi nt %hypv hcal

11 51 0 38 0. 9 305. 49 29. 95 0. 08 68604 3 70. 1 693

06==============================================================================LCPU mi npf maj pf i nt r csw i csw r unq l pa scal l s usr sys _wt i dl pc l cCpu0 0 0 17494 34037 16763 0 100 17438 9 42 0 49 0. 18 151Cpu1 0 0 12793 25479 12764 0 100 12737 9 39 0 53 0. 13 155Cpu2 0 0 51492 80030 28623 1 100 51516 12 62 0 25 0. 32 125Cpu3 0 0 41287 88098 46917 0 100 41251 10 50 0 39 0. 29 253

Logical CPU view

app (Available Pool Processors) if set



IBM System p


Shared processor pool util ization authority

Check box for

shared processor

pool info (app)from lparstat and

topas



IBM System p


topas –C flag# topas –C ( Wai t a coupl e mi nut es)

Topas CEC Moni t or I nt erval : 10 Mon Oct 22 15: 35: 15 2007

Par t i t i ons Memory ( GB) ProcessorsShr : 4 Mon: 2. 0 I nUse: 1. 8 Shr : 1. 2 PSz: 2 Don: 0. 0 Shr _PhysB 1. 79

Ded: 0 Avl : - Ded: 0 APP: 0. 2 St l : 0. 0 Ded_PhysB 0. 00

Host OS M Mem I nU Lp Us Sy Wa I d PhysB Vcsw Ent %Ent C PhI

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - shar ed- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

sys15_ni m1 A71 U 1. 5 1. 5 4 10 49 0 40 0. 93 73842 0. 30 310. 2 9

sys15_ni m2 A71 U 1. 5 1. 5 4 9 47 0 42 0. 84 74366 0. 30 281. 3 13

sys15_ai x1 A61 U 4. 0 3. 9 4 0 1 0 98 0. 01 720 0. 30 3. 2 0

sys15_ai x2 A71 U 3. 5 3. 4 4 0 0 0 98 0. 01 675 0. 30 2. 8 0

Host OS M Mem I nU Lp Us Sy Wa I d PhysB Vcsw %i st l %bst l

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - dedi cat ed- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

System wide view



IBM System p


Use lparstat –i to look at HMC set options# lparstat -iNode Name : sys02_ai x1

Par t i t i on Name : sys02_ai x1

Par t i t i on Number : 5

Type : Shar ed- SMT

Mode : Uncapped

Ent i t l ed Capaci t y : 0. 30

Par t i t i on Gr oup- I D : 32771

Shar ed Pool I D : 0

Onl i ne Vi r t ual CPUs : 2

Maxi mum Vi r t ual CPUs : 2

Mi ni mum Vi r t ual CPUs : 1Onl i ne Memor y : 1024 MB

Maxi mum Memor y : 4096 MB

Mi ni mum Memor y : 512 MB

Vari abl e Capaci t y Wei ght : 128

Mi ni mum Capaci t y : 0. 10

Maxi mumCapaci t y : 2. 00

Capaci t y I ncrement : 0. 01

Maxi mum Physi cal CPUs i n syst em : 2Act i ve Physi cal CPUs i n system : 2

Act i ve CPUs i n Pool : 2

Unal l ocated Capaci t y : 0. 00

Physi cal CPU Per cent age : 15. 00%

Unal l ocat ed Wei ght : 0



IBM System p


Some Advantages

Shared processor pools can allow better utilization of CPU resources

– Partitions are guaranteed their “entitled” processing units

– Uncapped LPARs can compete for additional unused resources

– Priority is driven by the uncapped LPARs weights

– Limitations set by number of virtual processors within partition

Multiple shared processor pools can give an even more granular control over

how resources are used

– Partitions still have the same “entitled” values as before

– Level0 and Level1 resolutions gives predictable path for sharing unused

resources

– Has potential to save in application license counts



IBM System p


Everybody into the Pool




Questions?

James Nash

[email protected]

Documents

Mspp Aix Vug