Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

SAP® MaxDB - Volume Configuration

 

This page deals with information about SAP MaxDB configuration for data and log volumes.

WIKI Space Editor: Thiago Lüttig.

 

 

Answers

Raw Device <-> File System

We often got the question: Should I create SAP MaxDB volumes on raw devices or files?

A raw device is a hard disk or part of a hard disk that is not managed by the operating system. On Unix or Linux, you can configure raw device volumes for databases.

Handy Hint

SAP recommends raw devices for data volumes and log volumes on Unix. The database system can usually access raw devices faster than files. In addition, the operating system can usually boot raw devices faster, because it does not have to check the consistency of the file system.

The speed, with which the database system can read data from the volumes and can write data to the volumes, greatly influences the performance of the database. To achieve good performance when the database is operating later (DIRECT IO), see SAP note 993848 for information about creating and configuring volumes of file type.
back to top

Optimal Size of Data Volumes

With SAP MaxDB the data is distributed evenly to all available data volumes. Volumes can be added to the productive system and the data distribution will include the new volume over time.

It is not only the size of a data volume that is important for system performance, but also the number of volumes. The number of volumes determines the scaling of the I/O. Depending on the number of configured volumes, SAP MaxDB configures threads (number of threads for each volume is configured using database parameter _IOPROCS_PER_DEV), which are responsible for the I/O.

We recommend the following values for database parameter _IOPROCS_PER_DEV: 2 (Unix), 1 (Microsoft Windows)
Therefore, subsequent I/O operations to a volume are distributed to several threads.

Handy Hint

You should increase the number of I/O threads for each volume if the database has been configured with a small number of data volumes, but the I/O system allows more parallel I/O.

 

However, it is advantageous to use an appropriately large amount of data volumes, because the data writer and user tasks must then check less frequently if an I/O queue is already busy.
Too many data volumes increase the number of threads, and can approach the limits of the operating system resources in this way.

Handy Hint

We recommend the following calculation formula (example):

Database Size
in GB

Number of
Data Volumes

Size of Volumes
(rounded) in GB

Size of Volumes
(rounded) in pages

10

4

2,5

327.680

50

8

6,25

819.200

100

10

10,00

1.310.720

200

15

13,33

1.747.190

500

23

21,74

2.849.505

1024

32

32,00

4.194.304

back to top

Log and Data Area on the Same Disk?

SAP recommends to configure log and data volumes separately on different disks.
The swap space should also be configured on a different disk.

back to top