MySQL Top Table IO Test
This test auto-discovers the top tables that are I/O intensive and for each table, reports the wait time and the read/write latency. Using this test, administrators can figure out the table that is experiencing slowness due to high read and write latencies.
Target of the test : A MySQL server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for every table in the target MySQL Database instance
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
Specify Host name of the server for which the test is to be configured in this text box. |
Port |
Specify the port to which the specified host listens in this text box. |
Database(DB) |
Specify the name of a database on the target MySQL database server being monitored in the Database text box. |
Username 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 in the Confirm Password text box. |
Allow Public Key |
By default, the Allow Public Key flag is set to No. But, if the specified USER is created with caching_sha2_password as the authentication plugin, then the eG agent can connect to the target database cluster using RSA public key. To this effect, you have to set Allow Public Key flag to Yes. |
SSL |
By default, the SSL flag is set to No, indicating that the target MySQL database server is not SSL-enabled by default. To enable the test to connect to an SSL-enabled MySQL database server , set the SSL flag to Yes. |
Verify CA |
If the eG agent is required to establish an encrypted connection with the target MySQL database server by authenticating the server's identity through verifying the server CA certificate, set Verify CA flag to Yes. By default, this flag is set to No. |
Truststore Password |
This parameter is applicable only if the Verify CA parameter is set to Yes. To verify the target server certificate, provide the password of the truststore file which contains the server CA certificate in the Truststore Password text box. By default, this parameter is set to none. |
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
Keystore Password |
This parameter is applicable only if the Verify CA parameter is set to Yes. To establish a connection with the target MySQL database server , the eG agent needs to have access to the client certificate. For this provide the password of the keystore file which contains the client certificate in the Keystore Password text box. By default, this parameter is set to none. |
Confirm Password |
Confirm the Password by retyping it in the Confirm Password text box. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Waits count |
Indicates the number of waits recorded on this table during the last measurement period. |
Number |
|
Average Wait time |
Indicates the average time spent by a query per wait to fetch data from this table during the last measurement period. |
Seconds/Wait |
|
Minimum wait time |
Indicates the minimum time spent by a query per wait to fetch data from this table during the last measurement period. |
Seconds/Wait |
|
Maximum wait time |
Indicates the maximum time spent by a query per wait to fetch data from this table during the last measurement period. |
Seconds/Wait |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is experiencing maximum wait time. |
Average read latency |
Indicates the average time taken to read from this table during the last measurement period. |
Seconds/Read |
|
Minimum read latency |
Indicates the minimum time taken to read from this table during the last measurement period. |
Seconds/Read |
|
Maximum read latency |
Indicates the maximum time taken to read from this table during the last measurement period. |
Seconds/Read |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is experiencing maximum read latency. |
Average write latency |
Indicates the average time taken to write into this table during the last measurement period. |
Seconds/Write |
|
Minimum write latency |
Indicates the minimum time taken to write into this table during the last measurement period. |
Seconds/Write |
|
Maximum write latency |
Indicates the maximum time taken to write into this table during the last measurement period. |
Seconds/Write |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is experiencing maximum write latency. |
Average fetch latency |
Indicates the average time taken to fetch the records from this table during the last measurement period. |
Seconds/Fetch |
|
Minimum fetch latency |
Indicates the minimum time taken to fetch the records from this table during the last measurement period. |
Seconds/Fetch |
|
Maximum fetch latency |
Indicates the maximum time taken to fetch the records from this table during the last measurement period. |
Seconds/Fetch |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is consuming maximum time to fetch records. |
Average insert latency |
Indicates the average latency noticed while inserting data into this table during the last measurement period. |
Seconds/Insert |
|
Minimum insert latency |
Indicates the minimum latency noticed while inserting data into this table during the last measurement period. |
Seconds/Insert |
|
Maximum insert latency |
Indicates the maximum latency noticed while inserting data into this table during the last measurement period. |
Seconds/Insert |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is consuming maximum time while data is inserted into the table. |
Average update latency |
Indicates the average latency noticed while updating this table during the last measurement period. |
Seconds/Update |
|
Minimum update latency |
Indicates the minimum latency noticed while updating this table during the last measurement period. |
Seconds/Update |
|
Maximum update latency |
Indicates the maximum latency noticed while updating this table during the last measurement period. |
Seconds/Update |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is consuming maximum time while updating the table. |
Average delete latency |
Indicates the average latency noticed while deleting this table during the last measurement period. |
Seconds/Delete |
|
Minimum delete latency |
Indicates the minimum latency noticed while deleting this table during the last measurement period. |
Seconds/Delete |
|
Maximum delete latency |
Indicates the maximum latency noticed while deleting this table during the last measurement period. |
Seconds/Delete |
Ideally, the value of this measure should be low. A sudden/gradual increase in the value of this measure is a cause of concern. Compare the value of this measure across tables to identify the table that is consuming maximum time while being deleted. |