Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

Windows system performance is slow because _mprosrv processes are paging

System is paging even though there appears to be available free memory.


The Windows Resource Monitor shows that _mprosrv processes have >0 hard faults/sec. Some are > 100/sec.

The Windows Resource Monitor shows that about 20% of memory is "In Use", almost all of the remaining memory is "Standby".

The Windows Process Scheduling Adjust for Best Performance has been changed from Background Services to Programs, but the problem still exists.

The problem is not seen when the databases are started using Progress Explorer or using the proserve command at a Windows command prompt.

FACT(s) (Environment):

The databases are started using the Windows Task Scheduler.
When starting the databases via the Windows Task Scheduler, the Windows Process Explorer Utility shows that the _mprosrv processes have a Memory Priority of 3.
When starting the databases via Progress Explorer or using the proserve command, the Windows Process Explorer Utility shows that the _mprosrv processes have the default Memory Priority of 5.
Windows Server 2008
OpenEdge 10.1C04 Service Pack

CAUSE:

The Windows Task Manager starts the _mprosrv processes with a lower then default memory priority. This is somehow causing the Windows Memory Manager to not use the available "Standby" memory, so the _mprosrv processes must page.
Currently no way has been found to set the Memory Priority of a process started by the Windows Task Scheduler.


FIX:

Start the databases via the AdminServer and dbman commands. When started this way, the _mprosrv processes will get the default memory priority of 5, even if started from the Windows Task Scheduler.