SAP ABAP Data Element SWLMEOBFRSHR (SAP Workload: Memory Released for Shared Objects (Bytes))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CCM-MON (Application Component) Monitoring
⤷
SAPWL_FRONTEND (Package) SAP: Workload Display, Enjoy & OO Version - ST03N

⤷

⤷

Basic Data
Data Element | SWLMEOBFRSHR |
Short Description | SAP Workload: Memory Released for Shared Objects (Bytes) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SWNCDOMDEC24 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 24 | |
Decimal Places | 0 | |
Output Length | 31 | |
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 | 0 | |
Medium | 20 | Mem. Rel.for Sh Objs |
Long | 40 | Memory Released for Shared Objects |
Heading | 50 | Memory Released for Shared Objects (Bytes) |
Documentation
Definition
During operation of the VMC, there are a number of different memory areas for which separate garbage collections are performed.
- All new objects are initially allocated to the young generation area. Once this is full, the area is cleaned by the garbage collector.
- All objects that have been referenced for a longer period of time are moved to the old generation area. When the memory use reaches a certain defined point, a garbage collection is performed here too.
- With the VMC, administration data and user data belonging to currently inactive users is stored in the shared memory like in ABAP. Garbage collections are also performed here when required.
This data element contains the total of the memory areas in bytes for the shared objects that were released by the garbage collection in question.
History
Last changed by/on | SAP | 20050627 |
SAP Release Created in | 710 |