Try OpenEdge Now
skip to main content
Managing ABL Applications
ABL and R-code Deployment and Management : Managing Client Performance : Procedure loading and execution : Using procedure libraries to improve r-code performance
 
Using procedure libraries to improve r-code performance
You can organize and store r-code in an ABL procedure library. The r-code files in a procedure library are known as members. Procedure libraries allow you to manage and execute r-code more efficiently.
OpenEdge provides two types of procedure libraries: standard and memory-mapped. A standard library contains r-code that executes in local memory. A memory-mapped library contains r-code that executes in shared memory. You create procedure libraries by using the PROLIB utility. For information about using the PROLIB utility to create and manage procedure libraries, see Managing Procedure Libraries.
When loading and executing r-code from operating system files in a directory, OpenEdge must open and close each file individually. When loading and executing r-code from standard or memory-mapped libraries, OpenEdge opens only one file—the library itself—to access all of the members in the library.
When you execute members from either a standard library in local memory or a memory-mapped library in shared memory, you gain the following advantages:
*Faster access to r-code
*Fewer file open and close operations
*Less I/O to temporary files
When you execute members from a memory-mapped library in shared memory, you gain the following additional advantages:
*Even faster access to r-code
*Requires less memory because multiple clients access the same r-code segments in shared memory