Measures reported by AsAbapMemTest
This test monitors the basic functions of the SAP Memory Management System and advises on how best to configure the system depending upon the platform used, the available resources, etc. It also sheds light on the hardware and operating system usage.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Ext_mem_actual_use |
The actual usage of extended memory. |
Percent |
|
| Ext_mem_attached |
The percentage of extended memory in user contexts that is active in WPs now. |
Percent |
|
| Ext_mem_slot_actual_use |
The percentage of extended memory slots actually used. |
Percent |
|
| Ext_mem_slot_total |
The number of extended memory slots. |
Number |
|
| Ext_mem_total |
Indicates the total size of the extended memory. |
MB |
|
| Heap_mem_actual_use |
The percentage of heap memory actually used. |
Percent |
Heap memory is a local memory assigned for the work process in SAP. Heap memory contains user contexts. Typically, if a dialog work process fully utilizes the extended memory, it starts . Once the heap memory is assigned to a work process, the work process will switch to the PRIV mode. This means that the work process is reserved for processing the current user context until the context releases the work process again when the request has ended.
If this measure reports a non-zero value, it implies that heap memory has been used – i.e., one/more work processes are in the PRIV mode.
For best performance, not too many dialog work processes should be in the PRIV mode simultaneously. So, if this measure reports a high value, then check the |
| Heap_mem_total |
The total size of heap memory (private memory). |
MB |
|
| Private_work_procs |
The number of restarted private work processes. |
Number |
|
| Dlg_work_procs_restart |
The number of restarted dialog processes. |
Number |
|
| Non_dlg_work_procs_restart |
The number of non-dialog processes restarted. |
Number |
|
|