About the White Paper:
Are you still stuck in BP0? No installation should still be using only one pool! Even systems using as few as 6000 buffers can get better performance with the same memory across more than one pool! Proper sizing of the pools and placement of objects can provide dramatic application performance improvements. With the arrival of version 3, we went from an environment that was tunable, to infinite tuning possibilities. The most difficult part of the tuning process is determining which objects to place in a pool, and pool sizing to optimize performance. While general shotgun approaches, such as placing all indexes into one pool and sort/work into another, usually provide substantial gains, the scientific placement and optimization of pool sizes will provide major additional performance improvements. This article addresses all of these issues, as well as all the effects of the new alterable tuning thresholds with version 3. Before and after examples of tuning scenarios and the performance improvements from several installations are illustrated, as well as one installation that saved 144 Megabytes of memory while reducing average transaction elapsed times. The basic steps and necessary information for effectively tuning the pools are applicable to releases of DB2 prior to version 3 as well as version 4.1 and future releases. |
