Kbase P27888: What is the Maximum Private Buffers per Connection (-Bpmax) parameter
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/20/2004 |
|
Status: Unverified
GOAL:
What is the Maximum Private Buffers per Connection (-Bpmax) parameter
FACT(s) (Environment):
Progress 9.1C
Progress 9.1D
FIX:
The Maximum Number of Private Buffers per Connection (-Bpmax) parameter is a database broker setting which controls the upper-limit of the number of private buffers a client connection can request at any given time through the Private Read-only Buffers (-Bp) client startup parameter.
-Bpmax n
where:
n is an integer specifying the maximum number of private buffers.
The number of blocks in the public database buffer is controlled by the Blocks in Database Buffers (-B) database startup parameter. Up to 25% of the blocks created may be allocated for use as private buffers at any time. When a client connects to a Progress database, the connection may request -Bp n private buffers. Prior to 9.1C, the maximum value of -Bp was hardcoded as 64. With the new -Bpmax parameter, the broker may override this limit by allowing the maximum value of -Bp requested to be up to the limit of private buffers (25% of -B).
An information message:
" The user requested n private read only buffers, but only t were available. (9952)"
Should a client connection request a -Bp value that is:
a) more than 25% of -B, or
b) more than the -Bpmax broker value limit per connection, or
c) more than the total number of private buffers remaining after subtracting the allocation of all other client's currently using private buffers (-Bp)
NOTE: Each use of a private read-only buffer reduces the number of public buffers. The total number of private buffers for all simultaneous users is limited to 25% of the total blocks in database buffers.
Max value: 25% of -B
Min value: 1
Single-user default: 64
Multi-user default: 64