Feedback
Did this article resolve your question/issue?

   

Article

How to determine an optimum before-image (BI) file cluster size

« Go Back

Information

 
TitleHow to determine an optimum before-image (BI) file cluster size
URL Name20566
Article Number000136094
EnvironmentProduct: OpenEdge
Version All supported versions
OS: All supported platforms
Question/Problem Description
How to determine an optimum before-image (BI) file cluster size
What should be my BI cluster size?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
This Article 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 bicluster 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 4 MB to 32 MB. The default is ½ MB (512 KB).

Determining the optimum bi cluster size is a reiterative process, that needs to be base-lined 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 you would therefore need to increase the current bicluster size, incrementally up to 4 times to increase the time it takes to fill the cluster by 4 times (120/30 = 4).

The bicluster size must be changed offline, optionally the biblocksize can be changed at the same time, through the following command syntax:
$   proutil <dbname> -C truncate bi -bi <clustersize in KB> -biblocksize <biblocksize in KB>
Example:
$   proutil <dbname> -C truncate bi -bi 16384 -biblocksize 16
Workaround
Notes
Last Modified Date11/20/2020 7:26 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.