Home
Some-cases if want to increase the memory parameters temporarily to accommodate some memory consuming tasks.
For example, their might be a scenario when some data intensive BW loads are running and your application team want to increase the memory temporarily.
In this case one can use "RSMEMORY" report to define memory allocation strategy.
Via "RSMEMORY" one can change the memory allocation for dialog or background processing.
In our example we will be increasing Heap memory from approx. 4GB to 6 GB on one of the application server.
Please note that "RSMEMORY" report will make change for only that server on which the report is executed.
The following memory classes exist:
SAP roll area, SAP Extended Memory, and private memory. These memory classes are assigned the following values,
which are also displayed in the initial screen of the rsmemory report.
The initial screen of the report comprises three parts:
•Quota Dialog:
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.
No entry in the memory class field corresponds to class 0 (heap memory).
The entry here does not have to match the defined memory parameters. If you enter a value for the heap memory in the 4th step that is different from the abap/heaparea_dia parameter, the value entered here takes precedence.
In this case, 1 MB of roll area is first allocated by a dialog work process, and then 300 MB of extended memory. Following this, 6.5 MB of roll area are allocated again before 200 MB of heap memory (the process then switches to PRIV mode) are allocated.
• Quota Batch/VB/Spool:
As is the case with the quota dialog, the allocation strategy for non-dialog work processes is defined here (see also Allocating Memory for User Contexts (UNIX)).
• Other parameters: You can change the following memory parameters here for test purposes (these changes only apply until the next server restart):
• abap/heap_area_dia
• abap/heap_area_nondia
• abap/heap_area_total
• em/stat_log_timeout
• em/stat_log_size_MBem/global_area_MB
Displaying the Memory Areas:
You can display a list of all the users on the application server, with their respective memory requirements, by choosing Goto → EM/HEAP areas. The used heap memory and extended of the user are displayed first, followed by the EM usage according to internal sessions.
This is followed by a history of users who have used more than the MB limit specified by em/stat_log_size_MB.
The available HEAP and EM memory is displayed at the end of the list.
EG Overview
The buttons EG Overview and EG Dump are used to analyze the Extended Global Memory. This is a part of the extended memory that is available for SAP-internal purposes. The parameter em/global_area_MB sets the size of Extended Global Memory.
Activities
In the initial screen of transaction
se38, enter the report rsmemory and choose Execute or F8.
Some-cases if want to increase the memory parameters temporarily to accommodate some memory consuming tasks.
For example, their might be a scenario when some data intensive BW loads are running and your application team want to increase the memory temporarily.
In this case one can use "RSMEMORY" report to define memory allocation strategy.
Via "RSMEMORY" one can change the memory allocation for dialog or background processing.
In our example we will be increasing Heap memory from approx. 4GB to 6 GB on one of the application server.
Please note that "RSMEMORY" report will make change for only that server on which the report is executed.
The following memory classes exist:
SAP roll area, SAP Extended Memory, and private memory. These memory classes are assigned the following values,
which are also displayed in the initial screen of the rsmemory report.
Value
|
Memory class
|
0
|
Roll area
|
1
|
Extended Memory (EM)
|
2
|
Private memory (heap)
|
The initial screen of the report looks like
this:
•Quota Dialog:
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.
No entry in the memory class field corresponds to class 0 (heap memory).
The entry here does not have to match the defined memory parameters. If you enter a value for the heap memory in the 4th step that is different from the abap/heaparea_dia parameter, the value entered here takes precedence.
In this case, 1 MB of roll area is first allocated by a dialog work process, and then 300 MB of extended memory. Following this, 6.5 MB of roll area are allocated again before 200 MB of heap memory (the process then switches to PRIV mode) are allocated.
• Quota Batch/VB/Spool:
As is the case with the quota dialog, the allocation strategy for non-dialog work processes is defined here (see also Allocating Memory for User Contexts (UNIX)).
• Other parameters: You can change the following memory parameters here for test purposes (these changes only apply until the next server restart):
• abap/heap_area_dia
• abap/heap_area_nondia
• abap/heap_area_total
• em/stat_log_timeout
• em/stat_log_size_MBem/global_area_MB
Displaying the Memory Areas:
You can display a list of all the users on the application server, with their respective memory requirements, by choosing Goto → EM/HEAP areas. The used heap memory and extended of the user are displayed first, followed by the EM usage according to internal sessions.
This is followed by a history of users who have used more than the MB limit specified by em/stat_log_size_MB.
The available HEAP and EM memory is displayed at the end of the list.
EG Overview
The buttons EG Overview and EG Dump are used to analyze the Extended Global Memory. This is a part of the extended memory that is available for SAP-internal purposes. The parameter em/global_area_MB sets the size of Extended Global Memory.
Activities
In the initial screen of transaction
se38, enter the report rsmemory and choose Execute or F8.
