Kbase P148184: Progress executables appear to be paging excessively.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/13/2010 |
|
Status: Verified
SYMPTOM(s):
Progress executables appear to be paging excessively.
As viewed using the svmon utility, the _mprosrv process paging increases over time from 10400 pages to 62227 pages.
FACT(s) (Environment):
AIX has 3 parameters that can affect the way the kernel will page computational and non-computational pages in memory - minperm%, maxperm% and maxclient%.
OpenEdge does not have any startup parameters that can influence or control how an operating system handles paging.
OpenEdge does have a -pinshm startup parameter (not available for AIX or Windows) that tells the operating system not to page out shared memory segments allocated on startup.
IBM AIX 5.3
OpenEdge 10.1B03 64-bit Service Pack
CAUSE:
System memory paging is controlled by the operating system, not by OpenEdge. The -pinshm startup parameter will designate to the operating system that the shared memory segments created by the database broker on startup are to be locked in memory, and not paged out. However, both the Windows and AIX operating systems do not support this option.
FIX:
This is expected behavior. Computational and non-computational memory paging is controlled by the operating system, not by OpenEdge. While it can be normal to see memory associated with OpenEdge processes being paged, AIX's Virtual Memory manager does have parameters (i.e. minperm%, maxperm%, maxclient%) that can be used to affect how and when paging occurs. Refer to the appropriate AIX documentation for more information on these parameters.