eG Monitoring
 

Measures reported by XMMemoryTest

This test monitors every memory type on the XenMobile JVM and reports how efficiently the JVM utilizes the memory resources of each type.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
usage_init Indicates the initial amount of memory allocated to this memory pool for memory management at startup. MB  
usage_used Indicates the amount of memory that is currently utilized by this memory pool. MB It includes the memory occupied by all objects, including both reachable and unreachable objects.

Ideally, the value of this measure should be low. A high value or a consistent increase in the value could indicate gradual erosion of memory resources. In such a situation, you can take the help of the detailed diagnosis of this measure (if enabled), to figure out which class is using up memory excessively.
usage_committed Indicates the amount of memory that is guaranteed to be available for use by this memory pool. MB The amount of usage_committed may change over time. The Java virtual machine may release memory to the system and committed memory could be less than the amount of memory initially allocated at startup. Committed will always be greater than or equal to used memory.
usage_max Indicates the maximum amount of memory that can be used for memory management by this memory pool. MB This is the difference between usage_committed and sum_used.

Ideally, the value of this measure should be high.
peakUsage_init Indicates the upper limit usage of the initial memory by this memory pool since startup of the JVM or since the peak was reset. MB  
peakUsage_used Indicates the upper limit usage of the memory that is currently utilized by this memory pool. MB  
peakUsage_committed Indicates the upper limit usage of the memory that is guaranteed to be available for use by this memory pool. MB  
peakUsage_max Indicates the upper limit of the maximum memory that can be used for memory management by this memory pool. MB  
collection_init Indicates the amount of initial memory that was utilized by this memory pool after the completion of the last garbage collection. MB  
collection_used Indicates the amount of used memory that was currently utilized by this memory pool after the completion of the last garbage collection. MB  
collection_committed Indicates the amount of committed memory that is guaranteed to be available for use by this memory pool after the completion of the last garbage collection. MB  
collection_max Indicates the amount of maximum memory that can be used for memory management by this memory pool after the completion of the last garbage collection. MB  
sum_init Indicates the total amount of memory initially allocated to the memory pools of this memory type at startup. MB This measure is applicable only to the Usage Summary descriptor.
sum_used Indicates the total amount of memory currently utilized by the memory pools of this memory type. MB This measure is applicable only to the Usage Summary descriptor.

Ideally, the value of this measure should be low. A high value or a consistent increase in the value could indicate gradual erosion of memory resources. In such a situation, you can take the help of the detailed diagnosis of this measure (if enabled), to figure out which class is using up memory excessively.
sum_committed Indicates the amount of memory that is guaranteed to be available for use by the memory pools of this memory type. MB This measure is applicable only to the Usage Summary descriptor.
sum_free Indicates the total amount of memory currently available for use by the memory pools of this memory type. MB This measure is applicable only to the Usage Summary descriptor.

Ideally, the value of this measure should be high.
sum_max Indicates the maximum amount of memory that can be used for memory management by the memory pools of this memory type. MB This measure is applicable only to the Usage Summary descriptor.
sum_percentage Indicates the percentage of memory utilized by the memory pools of this memory type. MB This measure is applicable only to the Usage Summary descriptor.

Ideally, the value of this measure should be low. A very high value of this measure could indicate excessive memory consumption by the JVM, which in turn, could warrant further investigation. In such a situation, you can take the help of the detailed diagnosis of this measure (if enabled), to figure out which class is using up memory excessively.