Kbase P115414: 4GL/ABL: What are Memory-Mapped execution environment limits?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/30/2008 |
|
Status: Verified
GOAL:
4GL/ABL: What are Memory-Mapped execution environment limits?
GOAL:
How much memory can a Memory-Mapped library use?
GOAL:
How much memory does a Memory-Mapped library library use?
GOAL:
How many Memory-Mapped r-code procedures can run at one time?
GOAL:
Does Progress manage the Memory-Mapped R-code Segments?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
The number of Memory-Mapped r-code procedures that can be run at one time and the memory used are determined by the following two factors:
1. The R-code Directory Size: The default maximum limit is 100 entries, the minimum is 5 entries, and the maximum is 500. The initial number of entries may be set by using the Directory Size (-D) startup parameter. Progress dynamically increases the directory size, as needed, up to the maximum.
2. The available memory: The number of open Memory-Mapped r-code libraries is limited by the amount of memory available on the system.
3. When Progress needs a Memory-Mapped R-code Segment, it executes the R-code Segment directly from memory. Progress does not store active Memory-Mapped R-code Segments in the execution buffer. Nor does it swap non-active R-code Segments to the session sort file.
4. Progress does not manage the swapping of R-code Segments. Progress relies on the operating system to manage the swapping of R-code Segments in and out of memory.