XM JVM Memory Details Test

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

Target of the test : A Citrix XenMobile

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every Memory Type:Memory Pool of XenMobile JVM 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

Initial usage

Indicates the initial amount of memory allocated to this memory pool for memory management at startup.

MB

 

Initial peak usage

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

 

Initial collection usage

Indicates the amount of initial memory that was utilized by this memory pool after the completion of the last garbage collection.

MB

 

Current usage

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.

Current peak usage

Indicates the upper limit usage of the memory that is currently utilized by this memory pool.

MB

 

Current Collection usage

Indicates the amount of used memory that was currently utilized by this memory pool after the completion of the last garbage collection.

MB

 

Committed memory

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

MB

The amount of Committed memory 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.

Committed peak usage

Indicates the upper limit usage of the memory that is guaranteed to be available for use by this memory pool.

MB

 

Committed collection usage

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

 

Max used

Indicates the maximum amount of memory that can be used for memory management by this memory pool.

MB

This is the difference between Committed memory and Current usage.

Ideally, the value of this measure should be high.

Max peak usage

Indicates the upper limit of the maximum memory that can be used for memory management by this memory pool.

MB

 

Max collection usage

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

 

Initial Memory

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.

Used Memory

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.

Committed memory

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.

Free memory

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.

Maximum memory

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.

Used percentage

Indicates the percentage of memory utilized by the memory pools of this memory type.

Percent

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.