Skip to main content



Database server

developerWorks

General DB2 Informix Oracle
   Recommendations  |   Performance papers  |   More
  FICON/ECKD or FCP/SCSI for database disks
  Scaling storage servers
  Disk setup
  Linux kernel 2.6 - I/O options
  ext2 or ext3 filesystem?
  Tuning read ahead / prefetch features
  31-bit vs. 64-bit database architectures
  Shared memory setup
  Swapping
Scaling storage servers

When vmstat indicates I/O wait times in case of an I/O bound workload, the latency of the storage subsystem limits the transactional throughput of the database. Using several storage servers in parallel can improve this limitation.

The following chart shows an example that uses storage servers of two different types named Type 1 and Type 2. Type 2's capacity is similar to the capacity of two servers of Type 1.

The usage of two Type 1 storage servers increases the throughput about 50% in comparison to a single Type 1 storage server.

Using all three storage servers together again increases the throughput about 50%. In all cases for the Linux point of view the database files are identical, only the disks belong to different storage servers.

Scaling storage servers, z900

Test environment
  • IBM eServer zSeries 900 (2064-216)
  • LPAR with 8 CPUs, 2GB memory
  • Novell/SUSE SLES 8 + SP2 for IBM zSeries (64-bit), kernel 2.4.19
  • Informix 9.4.0 FC3 (64-bit)
  • Benchmark Informix OLTP
  • Database data Logical Volume (LV): 8 CHPIDs, 8 host adapters, FCP/SCSI or FICON/ECKD disks in 8 ranks, ext2 filesystem

Conclusion: You can achieve a significantly higher I/O bandwidth if you distribute your database disks over several disk subsystems.


Back to top



Team
Please address any comments to the performance team: linux390@de.ibm.com