Kbase P14195: How to set up a deployment that uses memory mapped R-code libraries.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/11/2008 |
|
Status: Verified
GOAL:
How to create shared R-code libraries.
GOAL:
How to set up a deployment that uses memory mapped R-code libraries.
GOAL:
How to implement Progress shared Procedure Libraries?
GOAL:
What is the -makeshared option for the prolib utility?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1C
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
FIX:
Memory-mapped R-code libraries are recommended for deploying server-side code in a distributed environment, or for applications that run on self-service clients (as is usually the case when using terminal sessions).
Since the r-code in a memory-mapped library will be accessed though shared memory, multiple clients will use the same r-code segment and will therefore reduce memory usage on the server, as well as gain faster access to the r-code.
While the file size of the library will increase slightly, performance will be boosted significantly.
Memory mapped R-code libraries are generated from the standard libraries, using PROLIB:
prolib <standard-library-name> -makeshared <mapped-library-name>
For deployment and configuration purposes, the memory-mapped R-code library is treated the same as a standard one.