XM JVM Memory Usage Test

This test monitors the memory on the XenMobile JVM and reports how efficiently the JVM utilizes the memory resources.

This test is disabled by default. To enable the test, follow the Agents -> Tests -> Enable/Disable menu sequence in the eG administrative interface, pick Citrix XenMobile as the Component type, select Performance as the Test type, choose this test from the list of disabled tests list, and click on the < button.

Target of the test : A Citrix XenMobile

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the target XenMobile server that is being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port at which the specified host listens. By default, this is 4443.

Username and Password

Specify the credentials of a XenMobile user with Administrator privileges.

Confirm Password

Confirm the password by retyping it here.

SSL

Indicate whether/not the XenMobile server is SSL-enabled. By default, this flag is set to Yes

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Maximum memory

Indicates the maximum amount of memory allocated for the JVM.

MB

 

Used memory

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.

Used percentage

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.

Committed memory

Indicates the amount of memory that is guaranteed to be available for use by the JVM.

MB

 

Time taken for garbage collection

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.