SAP ABAP Data Element SVMCRT_PROF_SGC_RP_DURATION (Shared GC Statistics - Release Phase: Duration)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-VMC (Application Component) Virtual Machine Container
⤷
SVMCRT_ADMIN (Package) VMC Administration and Monitoring
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-VMC (Application Component) Virtual Machine Container⤷
SVMCRT_ADMIN (Package) VMC Administration and Monitoring
Basic Data
| Data Element | SVMCRT_PROF_SGC_RP_DURATION |
| Short Description | Shared GC Statistics - Release Phase: Duration |
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 | 5 | Durtn |
| Medium | 10 | Duration |
| Long | 15 | Duration |
| Heading | 20 | Duration |
Documentation
Definition
Time in microseconds between the start and finish of the release phase of this shared VM garbage collection.
Use
Dependencies
This value describes the time required for the kernel activity of this shared GC cycle. The cycle can take a lot longer if, for example, the contributions of the VMs take a long time coming.
The shared GC uses a distributed algorithm. A completed shared GC cycle has three phases:
- Start: A VM triggers the shared GC, for instance, through a full local VM GC. All shared VM objects are flagged and a list of VMs that have contributed to the GC is created.
- Contribution: All VMs in this list contribute by deleting the flags for the shared VM objects that they still reference. This first requires a full local GC within the VM.
- Release: Once all required VMs have made a contribution, the memory of objects still flagged is released.
With a forced shared GC cycle, all VMs that have not yet made a contribution are actively requested to do so as soon as they have reached a status that allows a full local VM GC.
With a non-forced shared GC cycle, VMs make their contribution by running a "random" full local VM GC.
A non-forced shared GC cycle can assume the status "forced" at any time.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |
