Kbase P14933: How to monitor memory usage with self service clients / agents shown in Task Manager
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
How to monitor memory usage with self service clients / agents shown in Task Manager
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
FIX:
There is a difference in the way the Task Manager reports the memory usage depending whether you are looking at the memory information in the 'Processes', or in the 'Performance' tab.
Just adding up the 'Mem Usage' column values from the 'Processes' tab will not equal the memory usage as reported by 'Commit Charge' in the 'Performance' tab.
The reason for this different reporting is that processes might require connection to the system's or other processes created shared memory, which will be added in their own reported working set. Because of this, it can be observed that the working set of the self service Progress session is very high - the parts of the connected database shared memory is also taken into account.
The memory usage that should be observed is located on the 'Performance' tab and it is named 'Commit Charge'.
It is necessary that 'Total' size of the 'Commit Charge' doesn't reach the 80% of the 'Total Physical Memory', because that is when the paging starts.
Therefore, the excessive memory usage of the Progress self service clients connected to the database using large database buffer pool can be safely ignored.