Kbase P111509: Progress application uses a lot of Paged Pool memory on Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/12/2005 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1E
Windows 2003
SYMPTOM(s):
Progress application uses a lot of Paged Pool memory on Windows
Application connects to the Progress database in shared-memory
Application connects to several databases
CAUSE:
One of the consumers of Paged Pool memory is open files. Self-serving clients have to open all the database files, so if there are hundreds of Progress clients running and the database has many extents, that adds up to a lot of open files.
FIX:
Use client / server connections instead of shared-memory connections and use memory-mapped procedure libraries to limit the use of Paged Pool memory.