Improving Db2 log performance
By understanding the day-to-day activity on the log, you can more effectively pinpoint when problems occur and better understand how to tune for best performance.
About this task
Db2 logs changes made to data, and other significant events, as they occur. The characteristics of your workload have a direct effect on log write performance. Long-running tasks that commit infrequently incur a lot more data to write at commit than a typical transaction. These tasks can cause subsystem impact because of the excess storage consumption, locking contention, and resources that are consumed for a rollback.
Do not forget to consider the cost of reading the log as well. The cost of reading the log directly affects how long a restart or a recovery takes because Db2 must read the log data before applying the log records back to the table space.