ztta/roll_area Classic roll area per user and internal mode usual amount of rol

l area per user and internal mode 3000000

The value specifies the size of the roll area in bytes.
The roll area is one of several memory areas, which satisfies the user requests
of user
programs. For technical reasons, however, the first 250 KB or so
of a user context are always stored in the roll area, further data
- up to the roll area limit ztta/roll_first,
- in the extended memory, up to the limit ztta/roll_extension or If extended mem
ory is exhausted, then
- again in the roll area, until the roll area is full, then
- in the local process area, up to the limit abap/heap_area_dia or abap/heap_are
a_total or until the address space or the swap space is exhausted.
Followed by termination with errors like STORAGE_PARAMETERS_WRONG_SET
an error code, that points to memory bottleneck
Aim:
Minimum data transfer with context change; however, the
increase helps to avoid problems (address space, swap space,
operating system paging)
ztta/roll_extension Amount of memory per user in extended memory (EM)
2000000000
Unit: Bytes
This value specifies the storage quantity in bytes that a dialog user context ca
n allocate (extended memory). The value refers to the storage quantity that an
external mode (=SAP window) allocates.
When the specified value is exceeded, memory from the roll area is allocated unt
il this is full. Local memory is then allocated.
( Data in the roll area is copied at context change When local memory within the
work process is allocated, the work process is assigned to this user context an
d is no longer
available for other user contexts (PRIV mode).)
If you set the value too high, a user could cause a bottleneck in the extended m
emory by increasing his user context Other smaller user contexts would
bring work processes to to PRIV mode before their allowed quota is reached.
Objective: Minimize no. of work processes in PRIV mode.
Allocate extended memory fairly.
Dependencies:
ztta/roll_extension only takes effect if its value is lower than em/initial_size
_MB is
ztta/roll_first: Extension saves extended memory, but causes increased load on t
he context switch
Database dependencies: None
Operating system dependencies: None
Database dependencies: None
abap/heap_area_total limit of heap on Appl.Server 2000000000
Unit: Bytes
Default : 800,000,000 (800 MB) (others)
2,000,000,000 (2 GB) (Windows NT) Increase the quota
Proposed value : Default value
The value must be configured so that a swap space overflow is avoided.
Who is permitted to make changes: The customer
Defines the local process memory quota (heap, malloc) for all user contexts of a
n SAP application server. The quota is used to avoid allocating swap space memor
y.
Dependencies:
Swap space in the operating system.
Swap space requirement for all other software, eg. operating systm
Database, R/3 instances and so on
Operating system dependencies: None
Database dependencies: None
Database system dependencies: None
abap/heap_area_dia limit of heap per Emode on Dialog processes. Heap memory
quota for dialog work processes.
Restriction of memory allocated to the heap with malloc for each dialog process.
2000000000
Unit: Bytes
Default : 80,000,000 (80 MB) (others)
2,000,000,000 (2 GB) (Windows NT) Increase the quota
Default value :
10 to 200 MB, according to the requirements of the ABAP program. Value 0 deactiv
ates this quota. Due to the risk of a swap space address space overflow, we stro
ngly advise you not to deactivate this quota.
Who is permitted to make changes: The customer
Description:
Defines the local process memory quota (heap, malloc) for a user context in a di
alog work process. The aim is to avoid a swap space bottleneck if a user context
becomes too large.
Operating system dependencies:
The maximum size of local process memory is below the limits set in the operatin
g system (configuration or architecture). Only some of these thresholds can be d
etermined with the test program 'memlimits' A value only takes effect if it is b
elow the maximum
size set by the operating system
Database dependencies: None
abap/heap_area_nondia Heap memory quota for spool / background /
update work processes
Parameters for background processes: Restriction of memory allocated to the heap
with malloc for each background process. 2000000000
Unit: Bytes
Default : 400,000,000 (400 MB) (other)
2,000,000,000 (2 GB) (Windows NT) Increase the quota
Default value :
Proposed value: 400 - 700 MB
Value 0 deactivates this quota. Due to the risk of a swap space address space ov
erflow, we strongly advise you not to deactivate this quota.
Who is permitted to make changes: Customer
Dependencies:
The value is only effective if it is lower than the value of abap/heap_area_tota
l
abap/heap_area_total is the limit for local process memory in alll work processe
s.
Operating system dependencies:
The maximum size of local process memory is below the limits set in the operatin
g system (configuration or architecture).
Only some of these thresholds can be determined with the test program 'memlimits
'
A value only takes effect if it is below the maximum size set by the operating s
ystem
Database dependencies: None
em/initial_size_MB Extended memory area from which all users of an applicat
ion server can satisfy their memory requirement 4092
Size of extended memory (Extended Memory)
Unit: 1 MB
Default : 128 (other)
= Profile parameter PHYS_MEMSIZE (Windows NT)
(See profil parameter: PHYS_MEMSIZE)
Who is permitted to make changes: The customer
Default value : (other)
200 - 500, in extreme cases much higher
- ca. 5MB x the number of active users on the application server
- Additional tuning acc. to the values from Transaction ST02
(For individual appl. servers) or RZ03 (for all appl. servers)
- From values > 500, you should expect operating system restrictions that cannot
be removed, particularly in 32 Bit systems.
Default value : (Windows NT)
Default = Do not change PHYS_MEMSIZE manually, since extended memory increases d
ynamically when necessary. No further calculation or adjustment is necessary.
Description:
Note the operating system dependency for Windows NT.
The value specifies the initial size of the memory area, which is managed by SAP
Memory Management as extended memory. This satisfies the storage requests of th
e interactive users' programs. This type of memory can be very quickly assigned
to changing work processes through 'mapping'. This enables rapid context change.
Aim:
Ideally this pool should be large enough to contain the total of all user contex
ts, so that the context change of all users can flow as quickly as possible. You
can limit the maximum consumption of a user by using the parameter ztta/roll_ex
tension. This can
prevent the extended memory being used up by users.
If the extended memory is exhausted, additional memory requests are satisfied fr
om the roll area and then from the local address area of a work process (heap, m
alloc).
The data in the roll area must be copied during context change, while the data i
n the local memory of the work process lead to exclusive assignment of entire wo
rk process (PRIV mode)
Dependencies:
The value must be smaller than/equal to (em/blocksize_KB * 16) and an exact mult
iple of (em/blocksize_KB / 1024).
- Address space limits for each process or in total
Operating system dependencies:
The swap space must be sufficiently large and should have a safety net of severa
l hundred MB for each event. Monitoring with ST06 or CCMS alerts RZ03
You may need to extend limits in the operating system:
- Maximum size of shared memory, mapped file, mprotect
- Address space limits for each process or in total
- etc.
You can use the test program 'memlimits' to determine these limits.