|
Measures reported by XMGarbageColTest
This test monitors the memory on the XenMobile JVM and reports how efficiently the JVM utilizes the memory resources.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| maximumMem |
Indicates the maximum amount of memory allocated for the JVM. |
MB |
|
| usedMem |
Indicates the amount of memory currently used. |
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. |
| usedPercent |
Indicates the percentage of used memory. |
Percent |
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. |
| committedMem |
Indicates the amount of memory that is guaranteed to be available for use by the JVM. |
MB |
|
| gcTime |
Indicates the time taken by the garbage collector for collecting unused memory. |
Secs |
Ideally, the value of this measure should be low. This is because, the garbage collection (GC) activity tends to suspend the operations of the application until such time that GC ends. Longer the GC time, longer it would take for the application to resume its functions. To minimize the impact of GC on application performance, it is best to ensure that GC activity does not take too long to complete. |
|