Determining The Number Of Connections Between The Host And Ds6000 - IBM TotalStorage DS6000 Series Redbooks

Extent
1GB
Figure 11-10 Spreading data across ranks
Note: The recommendation is to use host striping wherever possible to distribute the read
and write I/O access patterns across the physical resources of the DS6000.
The stripe size
Each striped logical volume that is created by the host's logical volume manager has a stripe
size that specifies the fixed amount of data stored on each DS6000 logical volume (LUN) at
one time.
Note: The stripe size has to be large enough to keep sequential data relatively close
together, but not too large so as to keep the data located on a single array.
The recommended stripe sizes that should be defined using your host's logical volume
manager are in the range of 4MB to 64MB.
You should choose a stripe size close to 4 MB if you have a large number of applications
sharing the arrays and a larger size when you have very few servers or applications
sharing the arrays.

11.4.4 Determining the number of connections between the host and DS6000

When you have determined your workload requirements in terms of throughput, you have to
choose the appropriate number of connections to put between your open systems and the
DS6000 to sustain this throughput.
A Fibre Channel host port can sustain a maximum of 206 MB/s data transfer. As a general
recommendation, you should at least have two FC connections between your hosts and your
DS6000.
232
DS6000 Series: Concepts and Architecture
Balanced implementation: LVM striping
1 rank per extent pool
Rank 1
Extent pool 1
Rank 2
Extent pool 2 Extent pool 2
Extent pool 3
Rank 3
Extent pool 4
Rank 4
LV stripped across 4 LUNs
Non-balanced implementation: LUNs across ranks
More than 1 rank per extent pool
Extent Pool
Extent Pool 5
2
GB LUN 1
Rank 5
2
GB LUN 2
Rank 6
Extent
1GB
Rank 7
2
GB LUN 3
Rank 8
2
GB LUN 4
8GB LUN