|
Measures reported by IBMDb2AppsTest
Sometimes the database performs poorly due, not to blocking, but to particularly heavy loads. Often the DBA will determine that the database simply cannot support the work that it is being asked to do and maintain adequate performance. This does not necessarily mean it is time to create more indexes or throw more hardware at the problem. One cannot always assume that periods of high utilization represent legitimate work. There could be problems in the applications that are running, or even problems caused by the user. To monitor the statistics pertaining to the different applications executing on a Db2 UDB Database server and their usage and identifies which program has more connections open to (i.e., processes running in) the Db2 database, eG enterprise offers IBMDb2AppsTest
This test auto-discovers applications running on each DB2 UDB instance on the target DB2 server, and reports which application has more connections open to (i.e., processes running in) the Db2 database. This test also reveals the application that consumed CPU for maximum time and required maximum number of direct read and write operations.
Outputs of the test : One set of results for each application running on each DB2 UDB server being monitored
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| ConnectionCount |
Indicates the number of connections that are currently established for running this application on this database instance. |
Number |
|
| MaxCPUTime |
Indicates the maximum time taken by CPU for executing this application. |
Seconds |
Compare the value of this measure across the applications to find out which application took prolonged CPU time.
The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text. |
| AvgCPUTime |
Indicates the average time taken by CPU for executing this application. |
Seconds |
|
| MaxDirectReads |
Indicates the maximum number of direct reads by this application. |
Number |
A high value over a period of time may be indicative of a performance bottleneck. The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text. |
| AvgDirectReads |
Indicates the average number of direct reads by this application per second. |
Reads/second |
|
| MaxDirectWrites |
Indicates the maximum number of direct writes by this application. |
Number |
The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text. |
| AvgDirectWrites |
Indicates the average number of direct writes by this application per second. |
Writes/second |
|
|