Configuring DS6KDS8K for Opt Perf

8/3/2019 Configuring DS6KDS8K for Opt Perf

1/63

IBM Systems and Technology Group

Las Vegas, NV

P03

Rosemary McCutchen

Configuring DS6000 and DS8000 for Optimal Performance

July 24 - 28, 2006

IBM Corporation 2006


2/63

2006 IBM Corporation

IBM TotalStorage

TrademarksThe following terms are trademarks of International Business Machines Corporation in the United

States, other countries or both.

AS/400, DS6000, DS8000, DS Storage Manager, Enterprise Storage Server, FICON, FlashCopy,GDPS, IBM, iSeries, pSeries, RS/6000, RMF, IBM TotalStorage, VM/ESA, VSE/ESA, xSeries, z/OS,zSeries, z/VM, On Demand Business

Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft, Windows and Windows NT are trademarks of Microsoft Corporation in the United States,

other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.


3/63


IBM TotalStorage

DisclaimerCopyright 2006 by International Business Machines Corporation.

No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation.

Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. Thisinformation could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s)and/or programs(s) at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or

withdrawal without notice, and represent goals and objectives only.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs orservices available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is

not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringeIBM's intellectually property rights, may be used instead. It is the user's responsibility to evaluate and verify the operation of any on-IBMproduct, program or service.

THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED.

IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted according to the terms and

conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement,etc.) under which they are provided. IBM is not responsible for the performance or interoperability of any non-IBM products discussedherein.

The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or

copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive

Armonk, NY 10504-1785U.S.A.


4/63


Configuring the DS6000/DS8000 forOptimal Performance

Rosemary McCutchenCertified Consulting IT SpecialistIBM Advanced Technical Support

[email protected]


5/63

2006 IBM Corporation5 Information On Demand |Information Assets and Systems

Objectives

Understand DS8000 and DS6000 hardware performance characteristics

Understand logical configuration considerations related to performance

Understand principles of DS performance optimization

Isolation Resource sharing

Spreading


6/63


DS8000 Hardware Performance Considerations

Front-end performance considerations

I/O ports Host adapters (HAs)

I/O enclosures

Servers (processors and memory)

Backend performance considerations

Ranks (and array type)

Device Adapter (DA) pairs



7/63


One server I/O loop

Maximum of 4 DA pairs

Order of installation of disks onDA pairs

2,0,3,1,2,0

64-disk increments

Disks ordered per frame

Larger disks installed first

Fully-populated 921

384 disks

DA2 and DA0 - 128 disks each


921 with 256 disks

Balanced configuration

Uses all 4 DA pairs equally

2107 Model 921 Disk Enclosures & Device Adapter Pairs

DA2

DA0

DA2

DA0

DA3

DA1


8/63


2107 Model 922 Disk Enclosures and Device Adapter Pairs

2 server I/O loops


Order of installation of disks onDA pairs

2,0,6,4,7,5,3,1,2,0

64 disk increments

Disks ordered per frame

Larger disks installed first

Fully-populated 922

640 disks


Other DA pairs 64 disks each

922 with 512 disks


Uses all 8 DA pairs equally


9/63


Storage Image 1(B)

1 server I/O loop


Installation order of disks

on DA pairs 0,4,5,1,0


256 disks (4 DAs)

2107 Model 9A2 Disk Enclosures & Device Adapter PairsStorage Image 2(A)

1 server I/O loop


Installation order ofdisks on DA pairs

2,6,7,3,2


256 disks (4 DAs)


10/63


DS8000 Application Performance Accelerator RPQ

For workloads requiring high bandwidthbut not a large number of disk drives

Normally, 64 disks required per DA pairbefore adding next DA pair

RPQ requires only 32 disks per DA pair

Currently DS8300 model 922 A+Bframes only

Allows use of more device adapters to

achieve higher bandwidth for a givenamount of disk capacity

Base Frame (A) Exp. Frame (B)


11/63


2107 Model 921 & 922 I/O Enclosures & I/O Ports (Base Frame)

Slot 0 1 2 3 4 5 0 1 2 3 4 5

For high performanceconnections, 2 I/O portsper FCP/FICON Host

Adapter recommended z/OS FICON

Express2 to DS ratioof 1:1recommended

z/OS FICON Expressto DS ratio of 2:1 may

be acceptable

For 2107 with all I/Oenclosures in use

Left enclosures (0,2)

are closer to server0 Right enclosures

(1,3) are closer toserver1


12/63


2107 Models 921 & 922 Host Adapter Installation Order (Base Frame)

15

1 2

3 4

5 6

7 8

9 10

11 12

13 14

16

Host adapter

installation sequenceis shown by numbers1-16

With an odd numberof host adapters,there will be anadditional adapter ina left (server0)enclosure

DAs will not be in useif associated disks

are not installed


13/63


2107 Model 922 I/O Enclosures & I/O Ports (1st Expansion Frame)

Slot 0 1 2 3 4 5 0 1 2 3 4 5

For high performanceconnections, 2 I/Oports per FCP/FICON

Host Adapterrecommended

z/OS FICONExpress2 to DS ratioof 1:1recommended

z/OS FICON

Express to DS ratioof 2:1 may beacceptable

For 2107 with all I/Oenclosures in use

Left enclosures arecloser to server0

Right enclosures arecloser to server1


14/63


15

1 2

3 4

5 6

7 8

9 10

11 12

13 14

16

2107 Model 922 HA Installation Order (1st

Expansion Frame)

Host adapter

installation sequenceis shown by numbers1-16

With an odd numberof host adapters,

there will be anadditional adapter in

a left (server0)enclosure

DAs will not be in use

if associated disksare not installed


15/63


I/O enclosures 0 and 1are dedicated to Storage

Image 1

I/O enclosures 2 and 3

are dedicated to StorageImage 2

Storage Images mayhave different number ofHAs installed

2107 Model 9A2 I/O Enclosures & I/O Ports (Base Frame)


16/63


2107 Model 9A2 Host Adapter Installation Order (Base Frame)

7

1 2

1 2

3 4

3 4

5 6

5 6

7 8

8

Host adapterinstallation sequence

is independent foreach Storage Image

Shown by

numbers 1-8

With an odd numberof host adapters,there will be anadditional adapter in

the left (server0)enclosure

DAs will not be in useif associated disksare not installed


17/63


I/O enclosures 4and 5 are dedicatedto Storage Image 1

I/O enclosures 6and 7 are dedicatedto Storage Image 2

Storage Imagesmay have differentnumber of HAs

installed

2107 Model 9A2 I/O Enclosures & I/O Ports (1st Expansion Frame)


18/63


7

1 2

1 2

3 4

3 4

5 6

5 6

7 8

8

Host adapterinstallation is

independent for eachStorage Image

Shown bynumbers 1-8

With an odd numberof host adapters,

there will be anadditional adapter ina left (server0)enclosure

DAs will not be in useif associated disksare not installed

2107 Model 9A2 HA Installation Order (1st Expansion Frame)


19/63


2107 Model 922 8-Host Adapter Ordering Option (Recommended)

5

____

0

____

1 2

X___

3

____

4 5

X___

0

____

1 2

____

3

____

4

5

__

__0

__

__1 2

X_

__3

__

__4 5

X_

__0

__

__1 2

__

__3

__

__4

5

____

0

____

1 2

X___

3

____

4 5

X___

0

____

1 2

____

3

____

4

5

__

__0

__

__1 2

X_

__3

__

__4 5

X_

__0

__

__1 2

__

__3

__

__4

I/O Enclosure 1

I/O Enclosure 2 I/O Enclosure 3

I/O Enclosure 0 I/O Enclosure 4 I/O Enclosure 5


DA2

DA2

DA3

DA0

DA1

DA4

DA5

DA5

DA6

DA7

DA7

DA6

DA0

DA1

DA3

DA4

4 adapters in base frame and 4 adapters in expansion frame

This is the most conservative approach for Host Adapter performance


20/63


2107 Model 9A2 8-Host Adapter Ordering Option (Recommended)

2 adapters in base frame and 2 adapters in expansion frame for each Storage Image

Image 1 Image 2

This is the most conservative approach for Host Adapter performance

5

__

__0

__

__1 2

X_

__3

__

__4 5

X_

__0

__

__1 2

__

__3

__

__4

5

_

_

__0

_

_

__1 2

X

_

__3

_

_

__4 5

X

_

__0

_

_

__1 2

_

_

__3

_

_

__4

5

__

__0

__

__1 2

X_

__3

__

__4 5

X_

__0

__

__1 2

__

__3

__

__4

5

_

_

__0

_

_

__1 2

X

_

__3

_

_

__4 5

X

_

__0

_

_

__1 2

_

_

__3

_

_

__4

I/O Enclosure 1


I/O Enclosure 0 I/O Enclosure 4 I/O Enclosure 5


DA

2

DA

2

DA

3

DA

0

DA

1

DA

4

DA

5

DA

5

DA

6

DA

7

DA

7

DA

6

DA

0

DA

1

DA

3

DA

4


21/63


DS8000 Memory Considerations

Processor memory

System memory (Cache)

Primarily affects read performance

Persistent memory (NVS)

Primarily affects write performanceDS8000 persistent memory scales with processor memory size

4GB128GB

2107 Models 922/9A2 only8GB256GB

2GB64GB

1GB32GB

2107 Model 921 only1GB16GB

SupportPersistent MemoryProcessor Memory


22/63



Front-end performance considerations

I/O ports Host adapters


Back-end performance considerations

Ranks (and array type)

Loops



23/63


DS6000 IRC Host Adapters & I/O Ports

Two 4-port

FCP/FICON

HAs

I0100 I0101 I0102 I0103

L0 L0

L0 L0

L1 L1

L1 L1

I0000 I0001 I0002 I0003

Server0

Server1

Each host adapter communicates with either server0 or server1

For availability, each z/OS or open systems host server should have 2connections (one to each DS6000 host adapter)

For open systems, Subsystem Device Driver Preferred Path will optimizeperformance

For remote mirroring, two dedicated I/O ports are recommended (one oneach DS6000 host adapter)


24/63


DS6000 Preferred Path

The preferred path function optimizessequential read performance

The preferred path function will direct:

I/O for LUNs 0000-3 to HBA 0

I/O for LUNs 0100-3 to HBA 1

The preferred path function is included in:

the IBM Subsystem Device Driver

z/OS operating system

0000 0001

0100 0101

0002 0003

0102 0103

Server0

Server1

AIX1

HBA 0

HBA 1

I/O portsAIX1 LUNs

AIX1 LUNs


25/63


DS6000 IRC Device Adapter and Disk Loops

One

DA Pair

(DA0)

Loop 0 Loop 1

I0100 I0101 I0102 I0103

L0 L0

L0 L0

L1 L1

L1 L1

I0000 I0001 I0002 I0003

Server0

Server1

DS6000 DA pair connects to both servers and both disk loops

Expansion units are connected to either Loop 0 or Loop 1

IRC is internally connected to Loop 0

Each disk loop is connected to both server0 and server1


26/63


DS6000 Disk Enclosures and Loops

Each block represents one 4-DDMarray site

Recommended order of installation of

disk enclosures on loops

0 (IRC),1,1,0,1,0,1,0

IRC disks are internally connected to

Loop 0

Balanced configuration with oddnumber of EX1s

Loop 1 will support more disks thanLoop 0 if there is an even number ofEX1s


27/63


Logical Configuration Considerations for Performance


28/63


Array Considerations

RAID type

RAID5 and RAID10 arrays perform equally for read

RAID5 array performs better for sequential write

RAID10 array performs better for random write

DS6000 Array size

8-DDM arrays are recommended unless there is a specific requirement for 4-DDMarrays

Sparing

Arrays without spares may mean better potential random performance

Array capacity should be confirmed after array creation

Array types (with spares and without spares) should be balanced across server0 andserver1 (when ranks are assigned to extent pools)

DS8000 - minimum of 4 spares per DA (64 or 128 disks) (single disk type)

DS6000 - minimum of 2 spares per 64 disks (single disk type0


29/63


2107 Model 922 RAID5 Example (Single Disk Type)

Each block representsone 8-DDM RAID5 array

Minimum of 4 spares perDA

First 4 arrays createdon DA contain spares

Single disk type example

Mixed disk types orRAID types may resultin creation of more 6+Parrays


30/63


DS6000 RAID5 Example (Single Disk Type)

Each block represents one 8-DDMRAID5 array

Minimum of 2 spares per 64 DDMs

Spares are assigned to array sites

and remain with those array sites,whether an array is created or not

Not necessarily on IRC and 1st

EX1 as shown

Array capacity should beconfirmed after creation

Single disk type example

Mixed disk types may result inmore 6+P arrays


31/63


Rank Considerations

A rank (and the underlying RAID array and array site) has no relationshipto server0 or server1 until after it has been assigned to an extent pool

Rank ID (Rx) does not indicate a server association unless specificallyconfigured to do so

Ranks should be assigned to server0 and server1 extent pools in abalanced manner

Ranks built on arrays containing spares should be balanced acrossserver0 and server1 extent pools

DS8000 ranks built on array sites associated with each Device Adapter

should be balanced across server0 and server1 extent pools

DS6000 ranks built on array sites associated with each disk loopshould be balanced across server0 and server1 extent pools


32/63


2107 Model 922 Ranks Balanced Across Servers Example

Each block representsone 8-DDM rankassigned to an extent

pool

Ranks on each DA arebalanced across server0and server1extent pools

Ranks with spares arebalanced across server0and server1 extent pools


33/63


DS6000 Ranks Balanced Across Servers Example

Each block represents one 8-DDMrank assigned to an extent pool

Ranks on each loop are balancedacross server0 and server1 extentpools

Ranks with spares are balancedacross server0 and server1 extentpools


34/63


Extent Pool Considerations

Single-rank extent pools are recommended unless there is aspecific requirement for multi-rank extent pools

Single-rank extent pools make it easier to map volumes to ranksand achieve uniform performance for volumes

Extent pools should be balanced across server0 and server1

Ranks should be assigned to server0 extent pools and server1extent pools in a balanced manner

Volumes should be allocated from server0 extent pools andserver1 extent pools in a balanced manner


35/63


Multi-Rank Extent Pool Considerations

All extents for a volume are allocated onone rank if possible

May change in the futureNo striping of extents for a single volume

across multiple ranks

Volume may spill across ranks if notenough extents are available on one rank

Volume may be larger than a single rank

Each new volume is allocated on the rankwith the most free extents

May change in the future

Standard volume size will result in roundrobin allocation of volumes across ranks

Same LSS will be used on multiple ranks

DSCLI showfbvol, showckdvol &showrankcommands may be used tomap volumes to ranks

Rank R2

Rank R0

2 A 1 0

2 A 1 1


36/63


Logical Subsystem/Logical Control Unit Considerations

For open systems, LSSs do not directly affect application performance

For z/OS, more LCUs will provide additional addresses for PAVs which canimprove performance

One or more unique LSS/LCU IDs consistently associated with a specific rankand DA or application may simplify performance analysis

Using one LSS/LCU across multiple ranks

Allows cross-rank copy services consistency grouping

May make performance analysis more complex


37/63


Logical Subsystem/Logical Control Unit Options

1.One unique LSS/LCU per rank

Simplifies management

2.Multiple LSSs/LCUs on one rank

Provides more addresses (& PAVs) forrank

Allows utilization of large drives withsmall volumes

3.One LSS/LCU on multiple ranks

Enables cross-rank Copy Servicesconsistency group

This will be typical for DS8000 multiple-rank extent pools

May make management more complex

00

2A

2A

01

2B

2B

Server0 Server1

Ranks/Pools Ranks/Pools

12 14 16 18 13 15 17 19

or

13 2312 22

15 2514 24


38/63


Logical Volume Considerations

Volume size

Volume size does not necessarilyaffect performance

For open systems, for a given amount of capacity, choose a volume sizesmall enough to allow volumes to be spread appropriately across all ranksavailable to an application workload

For z/OS, larger volumes may require more aliases (PAVs)

Volume placement

Logical volume placement on ranks, DAs (DS8000), loops (DS6000) andservers (server0 and server1) has a significant effect on performance

Logical volumes for each application workload should be allocatedaccording to isolation, resource sharing and spreading principles


39/63


z/OS Parallel Access Volumes (PAVs) Considerations

A successful IBM 2105 PAV strategy should also work well with the DS8000 and DS6000

Larger volumes require sufficient PAVs

Use dynamic PAVs and z/OS workload manager (WLM) if possible

Use the z/OS PAV Analysis Tool to analyze PAV use in existing systemswww.ibm.com->Servers ->mainframe->support->downloads->z/OS->z/OS Unix tools and toys

orhttp://www-03.ibm.com/servers/eserver/zseries/zos/unix/bpxa1ty2.html


40/63


Principles of DS Performance Optimization

Allocation of logical volumes and host connections for an application workload

Isolation

Resource sharing

Spreading

These principles are described in detail in Chapter 4 (4.1-4.3) of

IBM TotalStorage DS8000 Series: Performance Monitoring and Tuning SG24-7146.


41/63


Workload Isolation

Dedicating a subset of hardware resources to one workload

Ranks

I/O ports

Logical volumes and host connections for the workload are isolated to thededicated resources

Provides increased probability of consistent response time for an importantworkload, but

Maximum potential performance limited to the set of dedicated resources

Contention still possible for any resources which are not dedicated (e.g. processor,cache, persistent memory)


42/63


Workload Isolation (2)

Can prevent less important workloads with high I/O demands from impactingmore important workloads

It may be acceptable for multiple less important, I/O intensive resources to contendwith each other on a single set of shared resources (isolated from other workloads)

A good approach if workload experience, analysis or modeling identifies:

A workload which tends to consume 100% of resources available

A workload which is much more important than other workloads

Conflicting I/O demands among workloads

Rank level isolation may be appropriate for heavy random workloads

DA level isolation (DS8000) may be appropriate for large blocksize, heavysequential workloads


43/63


Workload Resource Sharing

Multiple workloads use a common set of resources

Ranks

I/O ports

Logical volumes and host connections for multiple workloads are assigned tothe shared set of resources

Provides higher potential performance by making a larger set of resources

available to a workload, but Possible contention for all shared hardware resources (e.g. ranks, I/O ports, Device

Adapters as well as processors, cache and persistent memory)

Good approach when not enough workload information is available to identifyisolation requirements

Also good for workloads that: Will not try to consume all of the hardware available

Peak at different times


44/63


Workload Spreading

Workload is balanced and distributed evenly across all allowed hardwareresources

Applies to both isolated and resource-sharing workloads

Logical volumes

Logical volumes for a workload are spread across:

Ranks Device adapters (DS8000)

Loops (DS6000) Server0 and server1

New logical volumes are allocated on least-used shared resources

Additionally, host logical volume striping may be used

Logical volume spreading exception

Files or datasets which will never be accessed simultaneously Multiple log files for a single application may be placed on the same rank


45/63


Workload Spreading (2)

Host connections

Host connections for a workload are spread across:

I/O ports Host adapters I/O enclosures (DS8000) Server0 and Server1

Both host adapters (DS6000)

Left side I/O enclosures and right side I/O enclosures (DS8000) New host connections are allocated on least-used shared resources

Additionally, multipathing software may be used


46/63


High I/O Demand Workload Examples Large-blocksize sequential

Logging

Sort/work

Business intelligence/data mining, data warehouse, decision support, Databasequeries

Disk copies

Backup/Restore Point-in-time Copy with background copy Remote mirror target volumes

Tape simulation on disk Video/imaging, film rendering

Life sciences

Batch

Small-blocksize random

Mail servers OLTP

Database


47/63


Identifying Workloads for Isolation or Resource Sharing Review service level requirements (workload importance) and application

history

Analyze workload characteristics

Read/write ratio

Random/sequential ratio

Average transfer size (blocksize)

Cache hit ratio

Average and peak workload (random I/Os, sequential MBs)

Peak periods

Copy services requirements

Link utilization and throughput (host connections and remote mirroring links)

Review the amount of capacity required (e.g. GB) and any volume size

requirements IBM and Business Partners can access Disk Magic tool to model DS hardware

requirements based on application characteristics


48/63


DS8000 Examples


49/63


DS8000 Rank Level Isolation Example

4 workloads (B,C,D,E)share 6 DA pairs

Each workload has 12dedicated ranks

2 on each of theshared DA pairs

Logical volumes for eachworkload are allocatedon its dedicated ranks onthe shared DA pairs

Device adapters are ashared resource

Additionally, host levelstriping may me usedacross multiple volumes


50/63


DS8000 DA Level Isolation Example

Workload A has 2dedicated DeviceAdapters

DA2 and DA0 (and all

ranks on these DAs)

Logical volumes forworkload A are isolated tothe 32 ranks on DA2 andDA0

The 32 ranks for workloadA are spread acrossserver0 and server1

16 ranks assigned toserver0 extent pools

16 ranks assigned toserver1 extent pools

Additionally, host levelstriping may be usedacross multiple volumes


51/63


DS8000 Rank Level Resource Sharing Example

4 workloads (B,C,D,E)

share 48 ranks on 6DA pairs

Ranks for theworkloads are spreadacross DAs as well as

server0 extent poolsand server1 extentpools

Additionally, host levelstriping should beconsidered


52/63


DS8000 Multiple Isolated Workloads DA Level Example

Workloads A&B share ranksand DAs with each other butare isolated from otherworkloads

Logical volumes forworkloads A and B areisolated to 32 ranks on DA2and DA0

Ranks for isolatedworkloads A & B are spreadacross DA2 and DA0 aswell as server0 extent poolsand server1 extent pools

Additionally, host levelstriping should beconsidered


53/63


DS8000 I/O Port Level Isolation Example

5

____

0

____

1 2

ABCD

3

____

4 5

ABCD

0

____

1 2

____

3

____

4

5

__

__0

__

__1 2

AB

CD3

__

__4 5

AB

CD0

__

__1 2

__

__3

__

__4

4 workloads (A,B,C,D) eachhave one dedicated I/O porton 4 shared host adaptercards

Ports for each workload arespread across HAs, I/Oenclosures and server0/1

Host adapter and I/Oenclosure are sharedresources

Additionally, multipathingsoftware should beconsidered



DA2

DA2

DA

1

DA

1

DA3

DA3

DA

0

DA

0


54/63


DS8000 Host Adapter Level Isolation Example

5

C___

0

D___

1 2

A___

3

B___

4 5

A___

0

B___

1 2

C___

3

D___

4

5

C_

__0

D_

__1 2

A_

__3

B_

__4 5

A_

__0

B_

__1 2

C_

__3

D_

__4

4 workloads (A,B,C,D) eachhave 4 dedicated hostadapters

1 HA in each base frameI/O enclosure

Workload may use 1 or

more ports per HA


I/O enclosure is a shared

resource

Additionally, multipathingsoftware should beconsidered



DA2

DA2

DA

1

DA

1

DA3

DA3

DA

0

DA

0


55/63


DS8000 I/O Port Level Resource Sharing Example

5

____

0

____

1 2

AB

CD_

__

3

____

4 5

AB

CD__

_

0

____

1 2

____

3

____

4

5

__

__0

__

__1 2

__

__3

__

__4 5

__

__0

__

__1 2

__

__3

__

__4

Host connections for workloadsA, B, C and D share 2 I/O

ports: 1 in a left-side I/O enclosure

1 in a right-side I/Oenclosure


Workload analysis should becompleted before planning to

share I/O ports Additionally, multipathing

software should be considered



DA2

DA2

DA

1

DA

1

DA3

DA3

DA

0

DA

0


56/63


DS6000 Examples


57/63


DS6000 Disk Capacity/Logical Volume Spreading Example

Logical volumes for the isolatedworkload (A) are spread across:

Ranks on Loop 0 and Loop 1

Ranks in server0 and server1extent pool

Logical volumes for the resource-

sharing workloads (B,C,D,E) arespread across:

Ranks on Loop 0 and Loop 1

Ranks in server0 and server1

extent pools

Additionally, host level stripingshould be considered


58/63


DS6000 I/O Port Level Isolation Example

I0100 I0101 I0102 I0103

L0 L0

L0 L0

L1 L1

L1 L1

I0000 I0001 I0002 I0003

Server0

Server1

The 4 workloads each have 2 dedicated I/O ports

1 I/O port on the Server0 Host Adapter(upper)

1 I/O port on the Sever1 Host Adapter(lower)

The ports for each workload are spread across Host adapters and server0/1

Additionally, multipathing software should be considered

A B C D

A B C D


59/63


DS6000 I/O Port Level Resource Sharing Example

The 4 workloads (A, B, C and D) share 2 I/O ports

1 I/O port on server0

1 I/O port on server1

The ports for the workloads are spread across Host adapters and server0/1

Additionally, multipathing software should be considered

I0100 I0101 I0102 I0103

L0 L0

L0 L0

L1 L1

L1 L1

I0000 I0001 I0002 I0003

Server0

Server1

AB

CD

AB

CD


60/63


Summary



DS6000 and DS8000 Logical Configuration Performance Considerations

Principles of Performance Optimization

Isolation

Resource sharing

Spreading


61/63


Related Sessions

Monitoring and Managing Performance Using TPC 3.1P07

DS8000 in a Microsoft Exchange EnvironmentD17

Best Practices Data layout for DS6000/DS8000D09

IBM TotalStorage DS Storage ManagerD04

DS Hardware Components and Logical Configuration ConceptsD03


62/63


DS8000 References

SG24-6452IBM TotalStorage DS8000 Series: Concepts and Architecture

SC30-4096Multipath Subsystem Device Driver Users Guide

SC26-7628IBM TotalStorage DS8000 Host Systems Attachment Guide

SC26-7623IBM TotalStorage DS8000 Users Guide

SY27-7641IBM TotalStorage DS8000 Installation Guide

GC35-0495IBM TotalStorage DS8000 Introduction and Planning Guide

SG24-6788-01

SG24-7146

IBM TotalStorage DS8000 Series: Copy Services in Open Environments

IBM TotalStorage DS8000 Series: Performance Monitoring and Tuning

SG24-6787-01IBM TotalStorage DS8000 Series: Copy Services with IBM eServer zSeries

SG24-6786-01IBM TotalStorage DS8000 Series: Implementation


63/63

Documents

Configuring DS6KDS8K for Opt Perf