Collector for ABAP Memory Monitoring

The technical name of the Collector for ABAP Memory Monitoring is /DVD/MON_CL_COL_BUFF.

This collector collects information about extended (global extended memory included), roll and paging memory usage for each application server of the SAP system.

The extended memory (EM) contains data associated with work processes, such as variables, lists and internal tables.

The global extended memory (EG) is part of extended memory (EM). It contains user-specific data and can be accessed by all work processes. The EG is a part of the EM, which is used for multiprocessing. The EG contains data that does not belong to a specific user session. For example, this might be data used for monitoring and statistics, table buffers of the database interface (DBI), or ABAP-shared objects that all work processes have access to independently of the user session.

The roll and paging buffers are the preferred working area of the roll and paging areas for an instance (application server). The remaining area is located on the disk as roll and paging files. The user context is stored in the extended memory and the roll area (when the job is rolled out of a work process). The paging area stores special data for the ABAP processor, while the extended memory stores a large portion of the internal tables of a program. This KPI shows the all-time peak usage of the paging memory.

Default KPIs Delivered with This Collector

The following default KPIs are delivered with this collector:

KPI name

Description

Unit

Collected for

Server specification

EMG_PEAK

All-time peak usage of the global extended memory

MB

Server

Any server

EMG_TOTAL

Total size of the global extended memory

MB

Server

Any server

EMG_USED

Global extended memory used

MB

Server

Any server

EMG_USED_P

Global extended memory used as a percentage

%

Server

Any server

EM_TOTAL

Total size of the extended memory

MB

Server

Any server

EM_USED

Extended memory used

MB

Server

Any server

EM_USED_P

ABAP extended memory used (server)

MB

Server

Any server

EM_USED_P_SYS_MAX

Maximum ABAP extended memory used (all servers)

%

System

Any server

PG_CFG_MEM

Paging area: Size in the shared memory (server)

MB

Server

Any server

PG_CFG_SYS_MEM

Paging area: Maximum size in the shared memory (all servers)

MB

System

Any server

PG_CFG_SYS_TOTAL

Paging area: Maximum size of the paging area (all servers)

MB

System

Any server

PG_CFG_TOTAL

Paging area: Size of the paging area (server)

MB

Server

Any server

PG_PEAK

Paging area: Peak paging area used (server)

MB

Server

Any server

PG_SYS_PEAK_MAX

Paging area: Maximum peak paging area used (all servers)

MB

System

Any server

PG_SYS_USED_MAX

Paging area: Maximum currently used paging area (all servers)

MB

System

Any server

PG_SYS_USED_P_MAX

Paging area: Maximum currently used paging area (all servers)

%

System

Any server

PG_USED

Paging area: Currently used paging area (server)

MB

Server

Any server

PG_USED_P

Paging area: Currently used paging area (server) as a percentage

%

Server

Any server

ROLL_USED_P

Roll area used

%

Server

Any server

ROLL_USED_P_SYS_MAX

Maximum roll area used (all servers)

%

System

Only application server

NOTE

If the calculated value for this KPI is greater than the maximum integer value, the maximum integer value 2147483647 is used as the KPI value. This is the maximum allowed value for the KPI.

NOTE The total size of the global extended memory (for example as shown by the report RSMEMORY) that is actually reserved by Application Server ABAP (AS ABAP) at the start is always higher than the value of em/global_area_MB. This is because AS ABAP needs to reserve additional space in the EG for ABAP shared objects.