Memory allocation sequence to dialog work processes

in SAP
This article answers the following queries:

What is the memory allocation sequence to dialog work processes in SAP?

When does a work process go to PRIV mode?

How to avoid or minimize work process going to PRIV mode ?

What are the SAP parameters used to define initial roll area, extended memory, heap
memory, roll area ?

Memory allocation sequence to dialog work processes in SAP :

--------------------------------------------------------------------------------------

1. Initially , a defined roll area is used. This roll area is defined by the SAP parameter
ztta/roll_first.
Usually ztta/roll_first is set to 1 in SAP so that only technically necessary amount
allocated to roll memory.

is

If the memory from the initial roll area( i.e. ztta/roll_first) is not sufficient for the user
context then
2. Extended memory is used until the extended memory is full or until the user quota
is reached
Extended memory is defined by the SAP parameter em/initial_size_MB and the user quota
for dialog workprocess is defined by the parameter ztta/roll_extension_dia.
If this memory is also not sufficient, then
3. The rest of the roll area is used. This roll area is defined by SAP parameter
ztta/roll_area.
Once this is also fully occupied then
4. The system is forced to use local heap memory (Private memory). Then the work
process goes into PRIV mode
Heap memory is available until one of the following occurs :
i)

Either the limit of the heap memory for dialog workprocesses

(abap/heap_area_dia)
or
the
entire
heap
memory
of
processes(abap/heap_area_total) for an application server reaches its limit.

is reached
all
work

ii)

Operating system limit for allocation of memory

iii)

The swap space in the host system is used up or the upper limit of the operating system
address space is reached.

The memory allocation strategy for dialog work processes, aims to prevent work processes
from allocating R/3 heap memory and thus entering PRIV mode.
When a work process enters PRIV mode, it remains connected to the user until the user
ends the transaction. Most of the time, we should try to avoid the situation of work process
going into PRIV mode for better performance of the SAP system. This can be done by
optimally defining abap/heap_area_total parameter.

Memory allocation sequence to non dialog work

processes in SAP
This article answers the following queries:

What is the memory allocation sequence to non dialog work processes (background,
update, enqueue and spool workprocesses in SAP?

What are the SAP parameters used to define initial roll area, extended memory, heap
memory, roll area ?

What is the memory allocation sequence to non dialog work processes in Windows
NT?

=================================================
Memory allocation sequence to dialog workprocesses is same in SAP for all the platforms.
However memory allocation sequence to non-dialog workprocesses is bit different based on
Platform. In Windows NT, memory allocation sequence for non-dialog workprocesses is same
as that of dialog workprocess memory allocation sequence in other platforms.

Memory allocation sequence to non dialog work processes in SAP as below (except in
windows NT) :
1. Initially memory is assigned from the Roll memory. Roll memory is defined by SAP
parameter ztta/roll_area and it is assigned until it is completely used up.
If the roll memory is full then
2. Heap memory is allocated to the non-dialog workprocess. Heap memory is available
until one of the following occurs :

Either the limit of the heap memory for non-dialog workprocesses is

reached (defined by the SAP parameter abap/heap_area_nondia) or
the entire heap memory of all workprocesses of an SAP application
server reaches its limit which is defined by parameter
abap/heap_area_total

Operating system limits of allocating memory

The swap space in the host system is completely used up. However
this situation should not occur often which results in severe
performance issues.Please check swap space requirements for various
platforms and define swap space optimally to avoid this issue.

If all the above mentioned heap memory is completely used up then a

non-dialog workprocess can use the SAP extended memory defined by
SAP parameter em/initial_size_MB.