Skip to end of metadata
Go to start of metadata

As described in the previous chapter, when the redo log is recorded during the transaction processing, the checkpoint step for the persistence of the memory DB, and the disk I/O for transaction processing of the disk DB are configured on the same disk, a disk bottleneck occurs. It is recommended to configure the redo log and each area as a physically separated disk in order to minimize the performance downgrade.

Disk I/O

As shown in the figure above, if the redo log record, checkpoint, and disk I/O by the buffer manager are concentrated on one disk, the disk bottleneck cannot be avoided. Therefore, it is recommended for the user to refer to this document for efficient disk configuration.

Configuration Example (1)

The following configuration is recommended, even if the configuration is difficult due to the environment of the system, the redo log and others must be configured as physically separated.


Disk configuration



Redo log


Data space (Memory DB)


Data space (Disk DB)


Data space (Disk Index)


Disk DB Undo space


  • ALTIBASE HOME is a space that stores files such as binaries, headers, and libraries for development and operation, as well as important trace logs that occur during the operation. So, it is recommended to be configured in a separate space.
  • In the case of a memory index, there is no separate disk I/O. This is because index re-configuration is performed on the memory after all the memory DBS are loaded in the ALTIBASE running stage. (There is no separate logging for memory index changes.)
  • It is recommended to separate the disk DB and the disk index for the purpose of minimizing disk I/O contention when performing I/O or DB change operations due to the expansion of each configured data file.
  • Considerations related to disk backup are not described in this document, so please refer to the "Backup/Recovery Guide".

Configuration Example (2)

This is the minimum separation configuration, and this configuration is recommended in the following environments.

  • When configuring with memory DB
  • When configuring a disk DB that does not have many changes in the operation
  • When it has the minimum DISK in the system environment


Disk configuration



Redo log


Such a configuration can reduce disk I/O contention only when the memory DB is mainly used or only in the service environment of the disk DB where there are not many changes.

Configuration Example (3)

This configuration is recommended when configuring various tasks and large amounts of data in a disk DB.

It is efficient from the point of view of distributing disk I/O by composing a separate tablespace by separating complex queries from simple processing queries, and configuring the physical data files of the tablespace into separate disks. However, the efficiency is low in an environment where disk buffer replacement is frequent.


Disk configuration



Disk DB-1 (complex operation)


Disk DB-2 (simple operation)


Redo logo


The location of the tablespace related to complex query execution and the method of locating the physical data files of the tablespace on a volume composed of separate disks, mainly for simple processing, can be effective in the sense of distributing disk I/O. However, even with such a configuration, it may be difficult to obtain the expected effect in an environment where buffer replacement is frequent.


  • No labels