Kbase 20207: How to Set the Private Read-Only Buffer (-Bp) at Runtime
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/07/2008 |
|
Status: Unverified
GOAL:
How to Set the Private Read-Only Buffer (-Bp) at Runtime
FACT(s) (Environment):
Progress 9.x
FIX:
This solution applies to Progress Client Version 9.x and later. It discusses the use of the buffer pool parameter (-Bp)at runtime in order to avoid over-working the buffer pool and slowing down the application.
During the execution of applications that read many records in order to generate reports or summarization, the buffer pool of the database can become clogged. This can cause a slowness of the entire application because of the buffer resources that are being requested by that specific client process. To avoid this problem, use the client parameter -Bp (private read-only buffers) to define a number of private buffers for the client to use to execute the heavy read application. From 9.1C and later, you can define up to 25% of the buffer pool for the parameter -Bp using the server startup parameter -Bpmax. The default value for -Bpmax is 64.
The client parameter can be very helpful, but sometimes it is very hard to predict when execution of the heavy read application will occur. Use of the -Bp as a default startup parameter could be unnecessary.
The answer is to change the -Bp parameter at runtime. If you use VST field _MyConnection._MyConn-NumSeqBuffers, you can use 4GL commands to enable the -Bp before run the report and disable it after the process finishes. The Database Administration Guide, Chapter 12.5.1, has a detailed guide to the -Bp parameter and how change it at runtime.
FIX:
Reference to Written Documentation:
Database Administration Guide and Reference Chapter 14, Section 5.1.