Pool Usage Suggestions

BP0 Catalog & Directory
BP1 Indexes Accessed Randomly
BP2 Indexes Accessed Sequentially
BP3 Tablespaces Accessed Sequentially
BP4 Tablespaces Accessed Randomly
BP5 DSNDB07

BP0 Catalog, Directory, Random Indexes (Small WkSet)
BP1 Indexes Accessed Randomly, (Med to Lg WkSet)
BP2 Indexes Accessed Sequentially
BP3 Tablespaces Accessed Sequentially
BP4 Tablespaces Accessed Randomly
BP5 DSNDB07

RAMO..S,M,L - Randomly Accessed ‘Mostly’ SAMO..S,M,L - Sequentially Accessed ‘Mostly’

Object Access Characteristics

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

Notes:

Two reasonable pool usage scenarios. Most installations should be able to optimize performance with 5 to 8 pools. While some installations might ultimately use a few more pools, too many simply means a lot more administrative work. I think that 10-12 might be an upper limit on effective pool and object tuning.

Remember that the pools are a system resource. While segregating them on an application basis might be nice for the application, it is unlikely this approach will provide the most efficient usage of pool and memory resources.