MySQL Wait Events Type Test
MySql wait event types include Lock (waiting for row/table locks), IO (disk or network input/output delays), CPU (waiting for processing time), and Concurrency (threads or connections contention). These types help pinpoint the exact resource causing query delays, enabling efficient performance tuning and system optimization based on where sessions are stuck.
Monitoring MySQL wait event types helps pinpoint resource bottlenecks like locks, I/O delays, or CPU contention. Understanding these wait sources enables targeted performance tuning, improves query efficiency, and ensures the database runs smoothly under load or high concurrency.
The MySQL Wait Event Type Test monitors the session wait events and collects metrics like number of waits, total wait time and average and percentage wait time etc. These metrics help administrators understand the performance implications of wait events and take preventive actions before the database performance drops.
Target of the test : A MySQL Database server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for the MySQL server being monitored
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the MySQL Database server. |
|
Port |
The port on which the server is listening |
|
Database |
Specify the name of the database that is to be monitored on the target MySQL Database server |
|
User and Password |
The eG agent has to be configured with the credentials of a user who has server-wide process and select privileges on the monitored MySQL server. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server |
|
Confirm Password |
Confirm the password by retyping it here. |
|
Idle Time |
Specify the time duration (in seconds) above which the processes that are waiting in the database will be regarded as idle. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Number of waits |
Indicates the total number of wait events of different types occurred during the operation of the database server. |
Number |
This is good measure of performance of the database server, if the number of wait sessions is high, it means the queries are waiting on something which help understand the slowness of overall database performance. |
|
Total wait time |
Indicate the total wait time including all wait types. |
Sec |
|
|
Average wait time |
Indicates the average wait time across all wait types and wait events . |
Sec |
If the average waiting time is very high it means that database each session has to wait before getting access to resources. You need to update the resource availability like I/O buses, CPU capacity and system memory etc. |
|
Percentage of wait time |
Indicates the total wait time as a percentage of time of operation of the the database server. |
Percentage |
If the percentage of wait is high it means the performance of the server is sub optimal as it is spending most of its time in waiting state. |