The rsmemory Report
You can use the rsmemory report to define your memory allocation strategy for work processes. You can specify the memory class assigned to a work process, the extent of the class assigned, and the order in which it is allocated. A distinction is made here between dialog work processes and non-dialog work processes (batch, update, spool).
The SAP system has the following memory classes:
-
Extended memory
-
Private memory (HEAP memory), consisting of:
- PRIV memory
- PROC memory
These memory classes are assigned the following values, which are also displayed on the initial screen of the rsmemory report.
|
Number |
Memory Class |
|---|---|
|
1 |
Extended Memory |
|
2 |
Private memory |
Starting the rsmemory Report
- Start transaction SE38.
- Enter report rsmemory in the input field, and to run the report choose
or F8.
Details of the rsmemory Report
The initial screen of the rsmemory report is split into three areas:
The allocation strategy for dialog work processes is defined here. You can specify the steps in which each class is allocated memory, and how much memory is allocated.
The entry here does not have to match the set profile parameters. If you enter a value for the private (HEAP) memory in the 4th step that is different from the abap/heaparea_dia profile parameter, the value entered here takes precedence.
The allocation strategy for non-dialog work processes is defined here. You can specify the steps in which each class is allocated memory, and how much memory is allocated.
The entry here does not have to match the set profile parameters. If you enter a value for the private (HEAP) memory in the 4th step that is different from the abap/heaparea_nondia profile parameter, the value entered here takes precedence.
The following profile parameters can be changed for test purposes. The change only applies until the next time the application server instance is started:
-
abap/heap_area_dia
-
abap/heap_area_nondia
-
abap/heap_area_total
-
em/stat_log_timeout
-
em/stat_log_size_MB
The two pushbuttons EG Overview and EG Dump are used for analysing the extended global memory. This is part of the extended memory available for internal SAP requests. The size is specified in the em/global_area_MB profile parameter.
The two pushbuttons Work Processes and PROC Overview ...
PROC memory allocates private memory (HEAP memory) in the system, and is not bound to a user context.
The Work Processes pushbutton is used to view the PROC memory allocation for each work process on the current application server instance. A list of all work processes in an application server instance is displayed, including the memory used by each work process.
The Server pushbutton displays the total consumption of the PROC memory on the current application server, and the maximum quota set in profile parameter em/proc_max_size_MB (if this parameter is set).
You can access more administration functions for PROC memory by choosing Goto. You can display a list of PROC memory users sorted by the highest consumption by choosing the following menu path: 
GoTo 
PROC Consumer List
You can display a list of PROC memory blocks currentöy allocated by the work process by choosing the menu path below. As soon as a block is no longer used, it is marked as free by the system.
Displaying Memory Areas:
To display a list of all the users on the application server instance, with their respective memory requirements, choose Goto EM/HEAP Areas. The private memory and extended memory used by the user are displayed first, followed by the extended memory according to internal sessions.
This is followed by a history of users who have used more than the MB limit set in em/stat_log_size_MB.
The private memory (HEAP) and extended memory (EM) that is still available is displayed at the end of the list.