SAP Note

88416 - Zero administration memory management for the ABAP server

Version 38 Validity: 04.09.2014 - active

Language English

Header Data
Released On
Release Status
Component

04.09.2014 15:17:09
Released for Customer
BC-OP-NT Windows

Other Components BC-INS-NT Installation Windows

Priority
Category

Recommendations / Additional Info

Special development

Symptom
Zero administration memory management on Windows

Other Terms
ZAMM, memory management, pagefilesize, page file size

Reason and Prerequisites

The zero administration memory management on Windows 32-bit and 64-bit systems that is described in this note requires no manual settings and
adapts itself dynamically to the memory requirements of the users.

Solution
Zero administration memory management on Windows
Description of functions
1. The basis for zero administration memory management on Windows is the dynamically self-extending extended memory. The extended
memory is initially set to the size of the profile parameter PHYS_MEMSIZE ([PM]). If more memory is required by the user, the extended
memory extends itself in steps of "min(([PM] / 2), 2)" up to the set limit of the profile parameter em/max_size_MB or until the address space
in the Windows page file is used up. By setting the standard value for em/max_size_MB to 20000 MB (100000 MB for 64 bit), it is the size of
the Windows page file that represents the actual limit for the extension of the extended memory. The profile parameter PHYS_MEMSIZE
determines how much of the entire main memory is to be used by the SAP system. The parameter is entered during installation in
accordance with the entry. The standard value for PHYS_MEMSIZE is the size of the main memory [RAM]. As of kernel version 7.20, you can
specify PHYS_MEMSIZE relative to the size of the main memory as follows:
PHYS_MEMSIZE=20%
Not all SAP versions provide you with the option of setting the maximum memory consumption individually in a dialog box during the
installation of the instance. In this case, the parameter is not set and receives the default value (size of the main memory [RAM]).
If you operate several SAP ABAP Server instances on one computer, you must set the parameter PHYS_MEMSIZE in the instance profiles.
For detailed information, refer to SAP Note 1518419.
2. Even with zero administration management, the Windows operating system should be configured in such a way that it keeps the file cache to
a minimum size. Therefore, make sure that indicator "Maximize Throughput for Network Application" is activated under 'Control Panel' ->
'Network' -> 'Services' -> 'Server' -> 'Properties'. This parameter can be set up to and including Windows Server 2003 only. This option no
longer exists for Windows Server 2008 and higher. The configuration takes place automatically.
On the 64-bit operating systems Windows Server 2003 and Windows Server 2008 (not Windows Server 2008 R2), if you use certain backup
software, the Windows file system cache may increase to high values and this may have a negative effect on the performance of the server.
For more information, see SAP Note 1416152.
3. The basis for the zero administration memory management is a sufficiently large Windows page file. For detailed information, refer to SAP
Note 1518419.
4. All relevant memory management parameters are predefined with an optimal standard value, making all manual configurations unnecessary.
Default values of zero administration memory management up to kernel version 7.20
[RAM] = size of the physical main memory
[PM] = value of the profile parameter PHYS_MEMSIZE (standard value=[RAM])
[US] = factor dependent on [PM] - calculated automatically
Profile parameter

Standard 32-bit Standard 64-bit Unit:

em/initial_size_MB

[PM]

[PM]

MB

em/max_size_MB

20000

1.5 * [PM]

MB

em/address_space_MB 512

4096

MB

ztta/roll_first

byte

ztta/roll_area

2000000

3000000

byte

ztta/roll_extension

2000000000

2000000000

byte

abap/heap_area_dia

2000000000

2000000000

byte

abap/heap_area_nondia 2000000000

byte

abap/heap_area_total

2000000000

[PM]*1048576 byte

rdisp/ROLL_MAXFS

[US] * 100

[US] * 100

8KB block

rdisp/ROLL_SHM

[US] * 100

[US] * 100

8KB block

rdisp/PG_MAXFS

32768

32768

8KB block

rdisp/PG_SHM

[US] * 50

[US] * 50

8KB block

Important:
"em/global_area_MB" + "abap/share_objects_size_MB" + "ztta/roll_extension"
mustfitinthefollowingaddresswindow:
"em/address_space_MB"
If ("em/global_area_MB" + "abap/shared_objects_size_MB") > "em/address_space_MB", the system does not start (error in "dev_disp"
dispatcher).
If ("em/global_area_MB" + "abap/shared_objects_size_MB") < "em/address_space_MB", ("em/address_space_MB"
"em/globa_area_MB" "abap/shared_objects_size_MB") is available for the extended memory. The value of "ztta/roll_extension" acts as a
quota.
At present, "em/address_space_MB" cannot be calculated automatically taking into account the specified parameters in kernel versions <
7.40.
Default values of zero administration memory management as of kernel version 7.40
[RAM] = size of the physical main memory
In 7.40, parameter values can contain formulas. The expression $(Parameter) in the value of a parameter references the value of the parameter
with the name Parameter.
Profile parameter

Standard 64-bit

Unit:

PHYS_MEMSIZE

1.0 * [RAM]

MB

em/initial_size_MB

0.7 * $(PHYS_MEMSIZE)

MB

em/max_size_MB

1.5 * $(PHYS_MEMSIZE)

MB

abap/buffersize

$(em/initial_size_MB)*1024*0.15

KB

abap/programs

$(abap/buffersize) / 4

Entries

abap/heap_area_dia

2000000000

byte

abap/heap_area_nondia

byte

abap/heap_area_total

1048576 * $(PHYS_MEMSIZE)

byte

abap/shared_objects_size_MB

$(em/initial_size_MB)*0.02

MB

em/address_space_MB

$(em/initial_size_MB)

MB

em/max_size_MB

$(PHYS_MEMSIZE)*1.5

MB

rdisp/wp_ca_blk_no

$(rdisp/elem_per_queue) * 3

Entries

rdisp/PG_SHM

max(min(1000+40*max(5,floor(($(PHYS_MEMSIZE)-128)
*25/128)),16384),1024)

8KB block

rdisp/PG_MAXFS

32768

8KB block

rsdb/ntab/entrycount

$(zcsa/db_max_buftab)

Entries

rsdb/ntab/ftabsize

min(500000,($(rsdb/ntab/entrycount)))

KB

rsts/ccc/cache07

$(rsts/ccc/cachesize) * 0.1

byte

rtbb/buffer_length

$(zcsa/table_buffer_area) * 0.1 / 1024

KB

rtbb/max_tables

$(zcsa/db_max_buftab) * 0.1

Entries

zcsa/table_buffer_area

max(30000000,$(em/initial_size_MB) * 1024 * 1024 * 0.05)

byte

ztta/roll_extension

2000000000

byte

1. In individual cases, customer-specific requirements may demand an individual parameterization. Here, we normally recommend the setting
of deviating values following an EarlyWatch Session.
2. If you want to use the default values that were calculated automatically, you must not list the relevant profile parameter in the instance profile or
Default.pfl. If you want to use transaction RZ10 to delete or deactivate the above mentioned profile parameters, use the "Extended
maintenance" function in RZ10. "Basic maintenance" is not suitable for deleting these parameters.
3. Zero administration memory management on Windows intends to reduce the number of relevant profile parameters. As a result, the

maintenance and configuration of the application server is simplified, and the available resources are optimally used.

Other Attributes
Operating system

NT/ALPHA
NT/INTEL
NT/INTELWIN2000

Validity
Software Component From Rel.
KRNL32NUC
4.6DEXT
6.40
7.00
7.10
7.20EXT
7.21
7.21EXT
KRNL32UC
6.40
7.00
7.10
7.20EXT
7.21
7.21EXT
KRNL64NUC
4.6DEXT
6.40
7.00
7.10
7.20EXT
7.21
7.21EXT
7.38
7.40
7.41
KRNL64UC
6.40
7.00
7.10
7.2L
7.20EXT
8.00
8.02
8.03
8.04
7.21
7.21EXT
7.38
7.40
7.41
KERNEL
4.6D
6.40
7.00
7.10
7.20
7.2L
8.00
7.38
7.40
7.41

To Rel.
And Subsequent
4.6DEX2

6.40EX2

7.01

7.20

7.20EXT

7.21

7.21EXT

6.40EX2

7.01

7.20

7.20EXT

7.21

7.21EXT

4.6DEX2

6.40EX2

7.01

7.20

7.20EXT

7.21

7.21EXT

7.38

7.40

7.41

6.40EX2

7.01

7.20

7.2L

7.20EXT

8.00

8.02

8.03

8.04

7.21

7.21EXT

7.38

7.40

7.41

4.6D

6.40

7.01

7.11

7.21

7.2L

8.04

7.38

7.40

7.41

Support Packages & Patches

Support Package Patches

Software Component
Support Package Patch Level
SAP KERNEL 7.41 64-BIT
SP004
000004
SAP KERNEL 7.41 64-BIT UNICODE SP004
000004

References
This document refers to:
SAP Notes
1518419 Page file and virtual memory required by the SAP system
1275873 Memory bottleneck during DDIC activation during EHP import
1009493 abap/heap_area* Parameter Defaults Changed (64-Bit Windows)
931024 FAQ: 64-bit platforms for Windows
923610 Memory parameter recommendations for banking systems
838866 REC: Memory requirement for logical database too large
745641 Memory-related terminations in Reporting Agent pre-calc.
407621 INST: 4.6C SR2 R/3 Inst. on Windows 2000: IBM AS/400
146289 Parameter Recommendations for 64-Bit SAP Kernel
129813 Windows: Problems caused by address fragmentation
110172 Windows: Transactions with large memory requirements
103747 Performance: Parameter recommendations as of Release 4.0

This document is referenced by:

SAP Notes (11)
1009493 abap/heap_area* Parameter Defaults Changed (64-Bit Windows)
745641 Memory-related terminations in Reporting Agent pre-calc.
931024 FAQ: 64-bit platforms for Windows
923610 Memory parameter recommendations for banking systems
838866 REC: Memory requirement for logical database too large
1926261 Central Note - Software Update Manager 1.0 SP11 [lmt_007]
1275873 Memory bottleneck during DDIC activation during EHP import
146289 Parameter Recommendations for 64-Bit SAP Kernel
407621 INST: 4.6C SR2 R/3 Inst. on Windows 2000: IBM AS/400
103747 Performance: Parameter recommendations as of Release 4.0
110172 Windows: Transactions with large memory requirements