2016-06-28 Page 1/6

88416 - Zero administration memory management for

the ABAP server
Version 41 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Special development
Release Status Released for Customer Released On 08.03.2016
Component BC-OP-NT (Windows)

Please find the original document at https://launchpad.support.sap.com/#/notes/88416

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
SAP 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%

NOTE: The specified value "20%" is an example of the specification of a percentage value and not a
suggested value for a productive system.

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.

1. 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

© 2016 SAP SE or an SAP affiliate company. All rights reserved

 1.
2016-06-28 Page 2/6
"Maximize Throughput for Network Application" is activated under "Control Panel -> Network ->
Services -> Server -> Properties". This parameter can be set only up to and including Windows Server
2003. 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.

2. The basis for the zero administration memory management is a sufficiently large Windows page file.
For detailed information, refer to SAP Note 1518419.

3. 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.2x

[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 1 1 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 0 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 (only valid for kernel < 7.40):

em/global_area_MB + abap/share_objects_size_MB + ztta/roll_extension

must fit in the following address window:
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

© 2016 SAP SE or an SAP affiliate company. All rights reserved

2016-06-28 Page 3/6

As of kernel version 7.40, certain profile parameters are calculated for all operating system platforms in
accordance with the available memory. It is also now possible to calculate parameter values with formulas.

[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

PHYS_MEMSIZE 1.0 * [RAM]
em/initial_size_MB 0.7 * $(PHYS_MEMSIZE)
em/max_size_MB 1.5 * $(PHYS_MEMSIZE)
abap/buffersize $(em/initial_size_MB) * 1024 * 0.15
abap/programs $(abap/buffersize) / 4
abap/heap_area_dia 2000000000
abap/heap_area_nondia 0
abap/heap_area_total 1048576 * $(PHYS_MEMSIZE)

abap/shared_objects_size_MB $(em/initial_size_MB) * 0.02

em/address_space_MB $(em/initial_size_MB)
em/max_size_MB $(PHYS_MEMSIZE) * 1.5
rdisp/wp_ca_blk_no $(rdisp/elem_per_queue) * 3
max(min(1000+40*max(5,floor(($(PHYS_MEMSIZE)-128)
rdisp/PG_SHM
*25/128)),16384),1024)
rdisp/PG_MAXFS 32768
rsdb/ntab/entrycount $(zcsa/db_max_buftab)
rsdb/ntab/ftabsize min(500000, ($(rsdb/ntab/entrycount)))
rsts/ccc/cache07 $(rsts/ccc/cachesize) * 0.1
rtbb/buffer_length $(zcsa/table_buffer_area) * 0.1 / 1024
rtbb/max_tables $(zcsa/db_max_buftab) * 0.1
zcsa/table_buffer_area min(3333333333, (max(30000000,($(em/initial_size_MB) * 1024 * 1024 * 0.1))))
ztta/roll_extension 2000000000

1. The formulas in the table are based on the 7.45 kernel version. They might be adjusted in later kernel
versions in line with observations from EarlyWatch sessions.
2. The calculated values from the kernel you use can differ from these. For detailed information, see
transaction SE38, report rsparam-either column 3 (System Default (Unsubs. Form)) or by
double-clickingon the parameter line, 1.1 C kernel.
3. This SAP Note will no longer be adjusted in line with changed formulas.
4. In individual cases, customer-specific requirements may demand an individual parameterization. Here,
we normally recommend the setting of deviating values following an EarlyWatch Session.
5. 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.
6. Zero administration memory management on Windows intends to reduce the number of parameters
entered into the profiles. As a result, the maintenance and configuration of the application server is
simplified, and the available resources are optimally used.

© 2016 SAP SE or an SAP affiliate company. All rights reserved

2016-06-28 Page 4/6

Software Components

Software Component Release

KRNL32NUC 4.6DEXT - 4.6DEX2

KRNL32NUC 6.40 - 6.40EX2

KRNL32NUC 7.00 - 7.01

KRNL32NUC 7.10 - 7.20

KRNL32NUC 7.20EXT - 7.20EXT

KRNL32NUC 7.21 - 7.21

KRNL32NUC 7.21EXT - 7.21EXT

KRNL32UC 6.40 - 6.40EX2

KRNL32UC 7.00 - 7.01

KRNL32UC 7.10 - 7.20

KRNL32UC 7.20EXT - 7.20EXT

KRNL32UC 7.21 - 7.21

KRNL32UC 7.21EXT - 7.21EXT

KRNL64NUC 4.6DEXT - 4.6DEX2

KRNL64NUC 6.40 - 6.40EX2

KRNL64NUC 7.00 - 7.01

KRNL64NUC 7.10 - 7.20

KRNL64NUC 7.20EXT - 7.20EXT

KRNL64NUC 7.21 - 7.21

KRNL64NUC 7.21EXT - 7.21EXT

KRNL64NUC 7.38 - 7.38

KRNL64NUC 7.40 - 7.40

KRNL64NUC 7.41 - 7.41

KRNL64UC 6.40 - 6.40EX2

KRNL64UC 7.00 - 7.01

KRNL64UC 7.10 - 7.20

KRNL64UC 7.2L - 7.2L

KRNL64UC 7.20EXT - 7.20EXT

KRNL64UC 8.00 - 8.00

© 2016 SAP SE or an SAP affiliate company. All rights reserved

2016-06-28 Page 5/6
KRNL64UC 8.02 - 8.02

KRNL64UC 8.03 - 8.03

KRNL64UC 8.04 - 8.04

KRNL64UC 7.21 - 7.21

KRNL64UC 7.21EXT - 7.21EXT

KRNL64UC 7.38 - 7.38

KRNL64UC 7.40 - 7.40

KRNL64UC 7.41 - 7.41

KERNEL 4.6D - 4.6D

KERNEL 6.40 - 6.40

KERNEL 7.00 - 7.01

KERNEL 7.10 - 7.11

KERNEL 7.20 - 7.21

KERNEL 7.2L - 7.2L

KERNEL 8.00 - 8.04

KERNEL 7.38 - 7.38

KERNEL 7.40 - 7.40

KERNEL 7.41 - 7.41

Support Package Patches

Software Component Version Support Package Patch Level

SAP KERNEL 7.41 64-BIT SP004 000004

SAP KERNEL 7.41 64-BIT UNICODE SP004 000004

This document refers to

SAP Note/KBA Title

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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved

2016-06-28 Page 6/6

407621 INST: 4.6C SR2 R/3 Inst. on Windows 2000: IBM AS/400

1518419 Page file and virtual memory required by the SAP system

1275873 Memory bottleneck during DDIC activation during EHP import

110172 Windows: Transactions with large memory requirements

103747 Performance: Parameter recommendations as of Release 4.0

1009493 abap/heap_area* Parameter Defaults Changed (64-Bit Windows)

This document is referenced by

SAP Note/KBA Title

1009493 abap/heap_area* Parameter Defaults Changed (64-Bit Windows)

923610 Memory parameter recommendations for banking systems

931024 FAQ: 64-bit platforms for Windows

1275873 Memory bottleneck during DDIC activation during EHP import

103747 Performance: Parameter recommendations as of Release 4.0

110172 Windows: Transactions with large memory requirements

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

1009493 abap/heap_area*: Parameter-Standardwerte geändert (64-Bit Windows)

923610 Memoryparameterempfehlungen für Banking Systeme

931024 FAQ: 64-Bit-Plattformen für Windows

1275873 Speicherengpass bei der DDIC Aktivierung beim EHP Import

103747 Performance: Parameterempfehlungen ab Rel. 4.0

110172 Windows: Transaktionen mit großem Speicherbedarf

838866 REC: Bedarf von Speicher für logische Datenbank zu groß

745641 Speicherbedingte Abbrüche in Reporting Agent Vorberechnung

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2016 SAP SE or an SAP affiliate company. All rights reserved