Simulate Performance Gains with Larger Pool Sizes

Start at Base Pool Size, and Evaluate Performance Improvements
Evaluate Average and Maximum Working Sets of Objects in a Pool
Small Variance of Avg/Max, and small Increases as Pool Increases...Good candidates to Group into a Pool

How Big ??????

Previous slide Next slide Back to the first slide View Graphic Version

Notes:

Pool tuning, sizing, and object placement is not a guessing game. It takes a large effort to get everything done properly, and once done, it must be monitored frequently and adjustments made. New applications come into the system, SQL is re-coded and access paths change, databases grow, etc. Monitoring should be done at least on a monthly basis, and bi-weekly is better on highly active systems.

Pool tuning, sizing, and effective object placement provides significant performance improvements...for the applications, for the DB2 system, for the DASD subsystem, and for the entire MVS complex.

If DB2 was really easy, and static, you would not be sitting here today because the corporations wouldn’t need any of us.