Tp Databases Test
This test reports statistics pertaining to the transaction processor’s database.
Target of the test : The TP server
Agent deploying the test : An internal agent
Outputs of the test : One set of outputs for every TP database 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 |
---|---|---|---|
Avg ADO response time |
Indicates the average ADO response time over the last minute. |
Secs |
A significant increase in the value of this measure denotes a slowdown of the TP database. |
Avg connections used |
Indicates the average number of connection s used in the last minute. |
Number |
|
Database pool size |
Indicates the number of connections that is available in the DBManager Connection Pool to execute transactions through ADO. |
Number |
Compare the pool size with the connections in use. If the connections is use approaches the pool size, you may want to resize the pool. |
Database pool availability |
Indicates whether the pool is available or not. |
Percent |
If the value of this measure is 0, it indicates that the pool is not available. The value 100, on the other hand, indicates that the pool is available. |
Request execution rate |
Indicates the rate of requests currently being executed through ADO. |
Reqs/Sec |
|
Requests waiting rate |
Indicates the rate at which requests are waiting to get executed. |
Reqs/Sec |
Ideally, this value should be close to 0. An increase in requests waiting for database execution could result in the login process being slow. |
SQL error rate |
Indicates the number of SQL errors thrown per second. |
Errors/Sec |
|
Avg transaction response time |
Indicates the average transaction response time during the last minute. |
Secs |
|