Kbase 20566: How to determine an optimum before-image (BI) file cluster size
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/28/2009 |
|
Status: Verified
GOAL:
How to determine an optimum before-image (BI) file cluster size
GOAL:
What should be my BI cluster size?
FACT(s) (Environment):
All Supported Operating Systems
FIX:
This solution provides guidelines on how to determine an optimum before-image (BI) file cluster size.
The BI cluster size determines the frequency of the number of checkpoints that are made:
In essence, a larger cluster size would mean less frequent checkpoints, longer recovery times and longer freeze when BI File grows. A smaller cluster size means that the checkpoints will happen more frequently.
Checkpoints should occur at least 60 seconds apart and a spacing of 5 minutes is better. Common cluster size ranges are 2 MB to 16 MB. The default is ½ MB (512 KB).
Determining the optimum bi cluster size is a reiterative process, that needs to be baselined against periods of "usual load" on the production database.
To examine checkpoint frequency, go to the following directory and sample at regular intervals:
Promon > R&D > 3 Other > 4 Checkpoints.
For example: "The suggested minimum for checkpoints is 120 seconds apart"
If the average length of time between any two checkpoints were found to be 30 seconds apart in the LEN column of the above promon output, and you would like to improve this by making the bi cluster take an average of 120 seconds to fill up, then 120/30 = 4. You would therefore need to increase the current cluster size, incrementally up to 4 times to increase the time it takes to fill the cluster by 4 times.
The cluster size must be changed offline through the following command syntax:
proutil <dbname> -C truncate bi -bi <clustersize in KB>