IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Performance tuning > Tivoli Data Warehouse > Relational database design and performance tuning for DB2 Database servers > Database design details > Logging
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Log performance
Ignoring the logging performance of your database can be a costly mistake, especially in terms of time. Optimize the placement of the log files for write and read performance, because the database manager must read the log files during database recovery.
To improve logging performance, use the following suggestions:
- Use the fastest disks available for your log files. Use a separate array or channel if possible.
- Use Log Retain logging.
- Mirror your log files.
Increase the size of the database configuration Log Buffer parameter (LOGBUFSZ). This parameter specifies the amount of the database heap to use as a buffer for log records before writing these records to disk. The log records are written to disk when one of the following points occurs:
- A transaction commits, or a group of transactions commit, according to the definition in the MINCOMMIT configuration parameter.
- The log buffer is full.
- Another internal database manager event occurs.
- Buffering the log records supports more efficient logging file I/O because the log records are written to disk less frequently and more log records are written each time.
- Tune the Log File Size (LOGFILSIZ) database configuration parameter so that you are not creating excessive log files.
Parent topic:
Logging