GemFire Resource Usage Test
By closely monitoring the reboot status, CPU usage, throughput and the I/O activity of each member, and comparing these metrics across members, you can quickly isolate resource-intensive members.
Target of the test : A GemFire Cluster server
Agent deploying the test : An internal/remote agent.
Outputs of the test : One set of results for each resource:member connected to the target GemFire server being monitored.
| Parameters | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port on which the specified host listens. By default, this is 7070. |
|
JMXPort |
Here, specify the port at which the jmx listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application |
|
JNDIName |
The JNDIname is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same. |
|
JMX UserName and JMX Password |
If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Configuring the eG Agent to Support JMX Authentication. |
|
Confirm Password |
Confirm the Password by retyping it in this text box. |
|
GemFire Servers |
Specify the name of the server if the monitored GemFire server belongs to a cluster. By default, this is none. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Is running? |
Indicates whether/not this member is currently running. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the member is currently running.. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 or 1. |
||||||||
|
Is rebooted? |
Indicates whether/not this member is rebooted. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the member is rebooted. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 or 1. |
||||||||
|
Active executions |
Indicates the number of executions i.e., Continuous queries (CQs) that were active for this member. |
Number |
|
||||||||
|
CPU usage |
Indicates the percentage of CPU utilized by this member. |
Percentage |
|
||||||||
|
Host CPU usage |
Indicates the percentage of time for which the CPU of this member's host was in use. |
Percentage |
|
||||||||
|
Uptime |
Indicates the total amount of time for which this member was up and running. |
Seconds |
|
||||||||
|
Total regions |
Indicates the total number of regions present in the cache allocated to this member. |
Number |
|
||||||||
|
Average reads |
Indicates the average rate at which data was read from the cache of this member. |
Reads/sec |
Compare the value of these measures across the members to figure out the most resource intensive member.
|
||||||||
|
Average writes |
Indicates the average rate at which data was written to the cache of this member. |
Writes/sec |
|||||||||
|
Data sent |
Indicates the amount of data sent from the cache of this member. |
MB/sec |
Compare the values of these measures across the members to figure out the member through which maximum amount of data is transmitted/received. |
||||||||
|
Data received |
Indicates the amount of data received by the cache of this member. |
MB/sec |
|||||||||
|
Clients connected |
Indicates the number of client connections to this member. |
Number |
|
||||||||
|
Total locator |
Indicates the total number of locators in the GemFire server. |
Number |
This measure is applicable only for the 'Summary' descriptor. |
||||||||
|
Total server |
Indicates the total number of backend servers communicating with the GemFire server. |
Number |
This measure is applicable only for the 'Summary' descriptor. |
