DS400 Storage Performance with Oracle
Performance sizing guideline for Storage SubSystems
To size a SAN Storage Subsystem for SAP means to size for I/O. The
needed capacity will be sized afterwards, if necessary at all. Storage performance is the key in all aspects of the sizing process. In any case number of disk is much more important than capacity of disks.
Before we start the sizing we have take into account that all DBs have
DATA files and REDO LOG files. Both have to be placed on different
disks.
ORACLE writes redo-Logs origlogA and origlogB, as well as the mirror-logs mirrlogA and mirrlogB.
They have to be placed on two RAID10 arrays, each containing only one logical-drive (Disk)
The file system on Disk 1 is holding origlog A and mirrlog B .
The file system on Disk 2 is holding origlog B and mirrlog A .
This combination guarantees best I/O performance.
Usually 2 physical disk are sufficient for one array (RAID1), only
larger DB instances need more disks, then configured as RAID10.
The data files (SAPDATA) have to be spread over as many disks as
possible, of course cost of these FC Disk have to be taken into account
.....
The distribution between read and write access is leading to read, if
no further data are available a distribution of 80% read and 20% write
can be assumed, with a read hit of 40%. For this IO pattern RAID5 is suitable.
DS4000:
One RAID array should be build of 5 to 10 disks.
At least two RAID-arrays are recommended - this is valid for small
system, and needs to be increased dependend on the IO requirements.
It is recommended to put only one logical-drive into one RAID-array, as well as stripping through the LVM
The total Number of disks is depending on the I/O demand:
At best the IO rate should be measured in real live .....
If you have to size for an upgrade use the current measured value, and calculate the increase.
If this is not possible here a rule of thumb: 2 SAPS generates 1 IO with 8 KByte
Through the Tool Disk Magic the number of disk can now be calculated.
For SAP disk with 15k rpm should be used only.
This leads to a absolute min configuration of 4 disks for the redo-logs, and 10 disks for the data file, total 14 disks.
This configuration is suitable just for very small SAP R3 installation, with no more than approx. 2000 SAPS.
This table shows configuration bases on SAPS.
Disk with 15K rpm with a RAID5, each with 5 disks, have been used.
Usable disk capacity for DB in GB |
|||||||
SAPS |
ReDo & archive Logs |
DATA RAID 5 (4+1) |
Spare disks |
Total number of Disk |
36 GB Disks |
72 GB Disks |
144 GB Disks |
1000
|
2
|
10
|
1 |
13
|
280
|
560
|
1 TB
|
2000
|
4
|
10
|
1 |
15
|
280
|
560
|
1 TB
|
3000
|
4
|
15
|
1 |
20
|
430
|
860
|
1.6 TB
|
5000
|
4
|
20
|
1 |
25
|
560
|
1.1 TB
|
2.2 TB
|
10000
|
4
|
40
|
1 |
45
|
1.1 TB
|
2.2 TB
|
4.4 TB
|
15000
|
8
|
60
|
2 |
70
|
1.7 TB
|
3.4 TB
|
6.8 TB
|
20000
|
8
|
80
|
2 |
90
|
2.2 TB
|
4.4 TB
|
8.8 TB
|