Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-RTA (Application Component) Runtime Analysis⤷
S_ABAP_TRACE (Package) ABAP TRACE
Basic Data
| Data Element | SATR_DE_STOR |
| Short Description | Current Memory Usage of a Trace Event |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | INT4 | 4-byte integer, integer number with sign |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 11 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Memory |
| Medium | 15 | Memory [byte] |
| Long | 20 | Memory [byte] |
| Heading | 20 | Memory [byte] |
Documentation
Definition
Current memory use at the time of a trace event in bytes. The value specifies the memory used by the internal mode and corresponds to the "Internal Mode Total (Used)" value of the memory analysis tool in the ABAP Debugger. Included in this are:
- The memory consumption of the ABAP application (total of memory use of all dynamic memory objects in ABAP such as class instances, anonymous data objects, internal tables, strings, and boxed components, as well as the static variables of all loaded programs, static attributes of all loaded classes, and the ABAP stack).
- Administration data of the ABAP Runtime other kernel components.
The total amount of virtual memory allocated to the operating system ("Internal Mode Total (Allocated)") is usually slightly more.
Memory use is measured when entering a procedural unit (for example, CALL METHOD) before the stack setup and when exiting a procedural unit (for example, ENDMETHOD) after the stack has been deconstructed.
Use
Using the difference in memory use from two related trace events (for example, METHOD - ENDMETHOD), it is possible to see the parts of an application where memory consumption has increased.
Memory use is displayed in the "Processing Blocks" view for methods, form routines, and function modules.
Memory use is displayed in the "Call Hierarchy" for every trace event (for example, operations on internal tables or database tables).
Dependencies
Example
Example 1:
Memory consumption of 100 bytes is measured when calling method m1 and a memory use of 150 bytes when leaving the method. The memory use has therefore increased by 50 bytes.
Example 2:
A local internal table itab_m2 has been defined in method m2. Method m2 attaches rows to this table but does not allocate any further memory. The memory use at the start and end of the method in the "Processing Blocks" view is therefore the same since the memory measurement takes place after the stack has been deconstructed.
However the temporary growth of the memory is displayed for the trace events of the internal table itab_m2 in the "Call Hierarchy".
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 700 |
