Measures reported by RabMQAppConnTest
Using this test, administrators can determine the different types of clients (Java clients, PHP clients, etc.) currently connected to the cluster and the number of current connections per type. This way, the test provides near-accurate indicators of the client connection load on the cluster. Also, by reporting the rate at which reductions and data are processed over the different types of client connections, the test reveals early to administrators if a specific type of clients are experiencing processing difficulties.
Outputs of the test : One set of results for each application currently connected to every node in the target cluster.
First-level descriptor: Node name
Second-level descriptor: Application process
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| count |
Indicates the total number of instances of this application process currently running. |
Number |
This is a good indicator of the connection load imposed by an application on a node.
Use the detailed diagnosis of this measure to view the top-10 (by default) connections made by this application, in terms of their reduction count. |
| diffDataReads |
Indicates the rate at which data was received from this application. |
Bytes/Sec |
|
| diffDataWrites |
Indicates the rate at which data was sent to this application. |
Bytes/Sec |
|
| diffReductions |
Indicates the rate at which reductions take place on this application. |
Reductions/Sec |
The reduction is a counter per process that is normally incremented by one for each function call. It is used for preempting processes and context switching them when the counter of a process reaches the maximum number of reductions. For example in Erlang/OTP R12B this maximum number was 2000 reductions.
The value of this measure represents the rate at which an application makes function calls. This is the real indicator of the workload generated by an application on the cluster. |
|