FAQ Memory usage for the ABAP Server on Windows
In Windows Task Manager for a disp+work.exe process, while in transaction SM50, the work process shows in "Waiting" state, what is the main cause for a high physical memory consumption?
In status waiting, when a work process which refers to disp+work.exe has been consuming physical memory in the task manager, this does not relate to a problem using or releasing memory at the level of OS.
In general this refers to the Operating System memory management releases memory of idle processes when memory is required for other processes this is process in which the Windows OS accomplishes the memory to perform better in a better manner.
All values which are greater than 2 GB for single processes are considered normal. The working set (memory) entails of shared memory pages along with private pages of a process which typically exist in the physical memory.
For instance, one can see high values when there is a big shared memory segment which has been set up similar to the ABAP program buffer.
The consumption of memory can be a problem, in case of a high virtual memory (physical memory + pagefile) usage (high commit charge) and/or a memory leakage.
How can we detect a memory leak of a process?
A memory leak persists when the private bytes or committed size of a process repetitively upsurges during runtime, until the entire virtual memory has been consumed.
There can be problem related to memory, when there are memory problems Incase you notice enormous "PRIVATE (KB)" or "COMMIT" values, typically for a process in Task Manager or Resource Monitor.
How can we configure memory, incase of two or more SAP instances have been installed on a Windows host?
During an SAP installation, the profile parameter PHYS_MEMSIZE have been set to the amount of physical memory which is available by default in the compute.
Ideally, to set up this parameter manually is done if there are two or more SAP instances on one box or in case you have another high memory consuming application running on the same box.
For instance, You can set parameter PHYS_MEMSIZE=50% for both, when there are 2 ABAP instances which have been installed on the same computer with same performance requirements. The sum of both parameters would be the size of the RAM (100%)
What are the possible origin of a memory dump with an error message "TSV_TNEW_PAGE_ALLOC_FAILED"?
Typically, the error can occur because of 2 major possibilities
Firstly, when the transaction or report runs out of memory quotas which have been stated in the profile parameters: abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total
And secondly, when the Operating System runs out of virtual memory (pagefiles and physical ram usage exhausted). The main reasons are:
- There is not sufficient virtual memory (RAM + pagefile) configured in the server
- Memory leaks in processes.
- Work processes consume a lot of heap memory (Often in background work processes).
Is it still recommended to set Windows page file = 3 to 4 times of the main memory (RAM) size?
This is a very old notion that was more meant for the old systems on Windows 32 bit platforms in which it is only possible to address 4 GB of physical memory.