Scribd
Upload
26 views3 pages

SAP Memory Management

Uploaded by

arunbehera83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
26 views3 pages

SAP Memory Management

Uploaded by

arunbehera83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

11/25/24, 11:28 AM

SAP Memory Management (BC-CST-MM)


Generated on: 2024-11-25 11:28:55 GMT+0000

| 1809 SP00

PUBLIC

Original content: https://help.sap.com/docs/ABAP_PLATFORM/f146e75588924fa4987b6c8f1a7a8c7e?locale=en-


US&state=PRODUCTION&version=1809.000

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not reflect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
11/25/24, 11:28 AM

Slow Response Times for Users

Problem Description
To process user requests, dialog work processes on Application Server ABAP (AS ABAP) allocate extended memory (EM), which
contains the user contexts, and which enables a fast context change. If the EM is full, SAP Memory Management assigns PRIV
memory (HEAP) to the dialog work processes. This memory is specific to the process. The work processes are switched to PRIV
mode, which locks them for a user context. If too many work processes are in PRIV mode, poor response times for some users can
be the result.

You can use transaction SM50 to determine how many work processes are in PRIV mode.

The following scenarios can lead to poor response times:

The limit is exceeded for the total extended memory (EM)

The total EM (em/initial_size_MB) has been used up by a few dialog work processes, which means that other work processes
cannot allocate any more memory areas from the EM, even though the EM quota for these work processes
(ztta/roll_extension) has not yet been reached. For this reason, the work processes switch prematurely to PRIV mode.

Solution:

Increase the size of the total SAP extended memory (em/initial_size_MB), to prevent work processes from being switched to
PRIV mode.

The EM quota for individual work processes is exceeded

The EM quota allocated by individual work processes is too low (ztta/roll_extension). The work processes, for which the
extended memory quota was exceeded, allocate PRIV memory and therefore switch to PRIV mode.

Solution:

Increase the quota for the extended memory using ztta/roll_extension.

High EM quota

The EM quota is too high. The total EM (em/initial_size_MB) is completely allocated by some work processes for larger user
contexts, whereby other work processes are switched to PRIV mode before their EM quota has been reached.

Solution:

Decrease the quota for the EM (ztta/roll_extension), or increase the size of the total extended memory
(em/initial_size_MB).

Related Information
Memory Allocation in SAP Memory Management
Extended Memory (EM)
PRIV memory (HEAP)
Monitoring PRIV Memory Consumption in the Work Process Overview (SM50)

This is custom documentation. For more information, please visit the SAP Help Portal 2
11/25/24, 11:28 AM
em/initial_size_MB: Full Size of the Extended Memory EM)
ztta/roll_extension: Quota for Extended Memory (EM)

This is custom documentation. For more information, please visit the SAP Help Portal 3

You might also like