Tibero SQL Workload Test
Nothing can degrade the performance of a Tibero database server like a resource-hungry or a long-running query! When such queries execute on the server, they either hog almost all the available CPU, memory, and disk resources or keep the resources locked for long time periods, thus leaving little to no resources for carrying out other critical database operations. This can significantly slowdown the database server and adversely impact user experience with the server. To ensure peak performance of the Tibero database server at all times, such queries should be rapidly identified and quickly optimized to minimize resource usage. This is where the Tibero SQL Workload test helps.
At configured intervals, this test compares the usage levels and execution times of all queries that started running on the server in the last measurement period and identifies a ‘top query’ in each of the following categories - CPU usage, memory usage, disk activity, and execution time. The test then reports the resource usage and execution time of the top queries and promptly alerts administrators if any query consumes more resources or takes more time to execute than it should. In such a scenario, administrators can use the detailed diagnosis of this test to view the inefficient queries and proceed to optimize them to enhance server performance.
Target of the test : A Tibero Database server
Agent deploying the test :An internal agent
Outputs of the test : One set of results for the target Tibero Database server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
The port to which the specified host listens. By default, the port number is 8629. |
User and Password |
In order to monitor a Tibero database server, a special database user account has to be created in every Tibero database instance that requires monitoring. A Click here hyperlink is available in the test configuration page, using which a new Tibero database user can be created. Alternatively, you can manually create the special database user. When doing so, ensure that this user is vested with the select any dictionary and create session privileges. The sample script we recommend for user creation for eG monitoring is: create user tibeg identified by tibeg default tablespace <users> temporary tablespace<temp>; grant create session, select any dictionary tibeg; The name of this user has to be specified in the User text box, and the password of this user has to be entered in the Password text box. This login information is required to query Tibero's internal dynamic views, so as to fetch the current status / health of the various database components. |
Confirm Password |
Confirm the Password by retyping it here. |
Tibero SID |
Specify the SID of the target Tibero database instance that is to be monitored in this text box. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Maximum physical reads |
Indicates the number of physical disk reads performed by the top query per execution. |
Reads/execution |
If the value of this measure is abnormally high, you can use the detailed diagnosis of this measure to view the top-5 (by default) queries generating maximum physical disk activity. From this, you can identify the top query in terms of number of physical disk reads. You may then want to optimize the query to reduce the disk reads. |
Maximum buffer gets |
Indicates the number of memory buffers used by the top query per execution. |
Memorybuffergets / execution |
If the value of this measure is abnormally high, you can use the detailed diagnosis of this measure to view the top-5 (by default) queries consuming memory excessively. From this, you can easily pick that query which is consuming the maximum memory. You may then want to optimize the query to minimize memory usage. |
Maximum CPU time |
Indicates the duration for which each execution of the top query was hogging the CPU resources. |
Secs/execution |
If the value of this measure is over 30 seconds, you can use the detailed diagnosis of this measure to the top-5 (by default) queries hogging the CPU resources. From this, you can easily pick that query which is consuming the maximum CPU. You may then want to optimize the query to minimize CPU usage. |
Maximum elapsed time |
Indicates the running time of each execution of the top query. |
Secs/execution |
If the value of this measure crosses 10 seconds, you can use the detailed diagnosis of this measure to view the top-5 (by default) queries that are taking too long to execute. From this, you can easily pick that query with the maximum execution time. You may then want to optimize the query to minimize execution time. |