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_STORDIFF |
| Short Description | Gross Memory Increase [byte] |
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 Inc |
| Medium | 20 | Memory Incre. [byte] |
| Long | 40 | Gross Memory Increase [byte] |
| Heading | 40 | Gross Memory Increase [byte] |
Documentation
Definition
The memory growth (in bytes) is the difference between the memory use at the time of a closing trace event (for example, ENDMETHOD, ENDSELECT, and so on) and the memory use at the time of an opening trace event (for example, CALL METHOD, SELECT, and so on).
Use
Using the difference in memory use from two related trace events it is possible to see the parts of an application where the memory use has increased.
Memory use is displayed in the "Processing Blocks" view for methods, form routines, and function modulesbaus.
Memory use is displayed in the "Call Hierarchy" for each trace event (for example, operationa 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 | 720 |
