Kbase P108298: What is the limit for -B in Version 8?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
03/06/2010 |
|
Status: Verified
GOAL:
What is the limit for -B in Version 8?
FACT(s) (Environment):
Progress 8.x
All Supported Operating Systems
OpenEdge Category: Database
FIX:
The Blocks in Database Buffers (-B) limit is listed as 500,000 in the Progress System Administration Reference book. This limit is for ProControl Limit.
The maximum setting for -B depends partially on platform and partially on how the operating system is tuned.
For DG/UX the setting may have as high as 125 million for -B.
For most other UNIX platforms 4 gigabyte can not be exceed .
Some operating systems are limited to 1.75 gig of ram which would be 1750000 based on the OS limit for shared memory.
What ever the size of the work space that is available to work with, all the program's code and data must be fit into it. This includes:
* The code for the program itself (the "text segment" on UNIX)
* Code in shared libraries or dynamic link libraries ("dll's")
the program uses
* The program stack
* Thread stacks
* Constant or static data
* Global variables
* The "heap", a pool of private memory from which space for various temporary data structures, like Progress widgets, r-code buffers, record buffers, etc. is taken from.
* Shared memory segments
* File buffers for open streams
* Memory mapped files
* etc
Many of these vary depending on what the 4GL application uses.
Note, if the application connects to more than one database as self-serving, then the shared memory segments from all the databases must be
attached at once. If -B is max out for all of them, it will probably not be possible.