Base Simulation.....Object Level

Results for Table Space....................................DB2PO.SOLNSORD

Object GetP total............................690,589 ( 29.0% of BP GetP)

Bpool Size GetP used Num. of Hits ApHit Ratio Avg. WSet Max. WSet

10,000 689,218 661,803 95.6 % 3,277 8,607

18,000 688,180 663,431 96.4 % 6,297 15,329

26,000 686,874 664,066 96.7 % 9,537 21,855

34,000 685,796 664,560 96.9 % 13,074 28,390

42,000 685,025 665,323 97.1 % 16,815 34,939

50,000 684,158 665,571 97.3 % 20,804 41,553

Bpool Size Pages Read Read I/O SyHit Ratio

10,000 198.5 /S 13.8 /S -2.1 %

18,000 198.8 /S 13.1 /S -1.6 %

26,000 201.2 /S 12.8 /S -1.2 %

34,000 203.3 /S 12.5 /S -0.8 %

42,000 204.8 /S 12.2 /S -0.5 %

50,000 208.1 /S 12.1 /S -0.2 %

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

Notes:

The simulation combines both simulation techniques and statistical analysis to provide useful information at the object level. The results from a simulation run must be analyzed in conjunction with a Statistical analysis that shows rates and type access for each object.

The Index object is ‘well behaved’, meaning the average and maximum number of pages in the pool (Working Set or WkSet) are not large, the maximum is not multiples of the average. and they don’t increase greatly as the pool size increases.

Note the increase in hit ratio as the pool increases from 5000 to 7000 buffers, and that the Index had 51.7% of the total getpage activity.

On the other hand, look at the difference between the Avg and Max WkSet for the tablespace, and the Max ranges from 75-80% of the total pool size. These must be separated into different pools.

The simulation analysis continues on the next slide.