Tp Regulators Test
This test monitors the performance of the regulator on a Transaction Processor (TP).
Target of the test : The TP server
Agent deploying the test : An internal agent
Outputs of the test : One set of outputs for every regulator monitored.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The host for which the test is to be configured. |
|
Port |
Refers to the port at which the specified host listens to. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Active requests |
Indicates the number of requests that are actively executing. If the regulator is enabled, this value will never exceed the value of RegulatorMaxActive on the TP. When a new request arrives, the server checks to see if it is already processing the maximum number of requests. If it has reached the limit, it defers processing new requests until the number of active requests drops below the maximum amount. |
Number |
The number of active requests should ramp up as new users are added and remain constant once the highest load is reached. |
|
Avg request wait time |
Indicates average time for which requests that began active execution in the past second had to wait on the Regulator. |
Secs |
|
|
Timed out requests |
Indicates the number of requests that timed out in the past second while waiting to become active. |
Number |
A high value of this measure generally means that there are too many users on the system and response times will be high. |
|
Waiting requests |
Indicates the number of requests that are waiting to begin active execution. |
Number |
If the value of this measure increases then it indicates that the time that will be spent on processing the transactions will increase as well. |
