MySQL Resources Test

This test measures the effect of query execution on the disk and memory resources of the MySQL server in terms of files opened, temporary files created, delayed thread inserts, active threads etc.

Target of the test : A MySQL server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the database being monitored

Configurable parameters for the test
  1. TEST PERIOD – How often should the test be executed
  2. Host – The IP address of the MySQL server
  3. Port – The port on which the server is listening
  4. db – the name of a database on the server
  5. Usernameand 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 topic.
  6. Confirm password – Confirm the password by retyping it here.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Open files

Indicates the number of files that were opened during the last measurement period.

Number

 

Created temporary files

Indicates the number of implicit temporary files that were created on the tables of the disk, while executing statements during the last measurement period.

Number

 

Ratio of created temp tables on disk

Indicates the percentage of temporary tables that were created on the disk, while executing statements on this node.

Percent

 

Opened tables cache hits

Indicates the number of hits for open tables cache lookups.

Number

 

Opened tables cache misses

Indicates the number of misses for open tables cache lookups.

Number

 

Opened tables hit ratio

Indicates the percentage of hits for open tables cache lookups.

Percent

Compare the value of this measure across nodes to figure out the node on which maximum percentage of hits for open tables cache lookups were noticed.

Delayed insert threads

Indicates the number of delayed insert handler threads that are in use.

Number

 

Slow launch threads

Indicates the number of threads that have taken more than slow_launch_time for creation on the database, during the last measurement period.

Number

A high value for this measure could cause excessive delay in processing new connection requests to the database server.

Threads active

Indicates the number of threads that are currently active.

Number

A high value for this measure is indicative of a high load on each node of the target cluster database server.

Threads cached

Indicates the number of threads in the thread cache of the database currently.

Number

 

Threads spawned

Indicates the number of threads newly created to handle new connections on the database during the last measurement period.

Number

Where possible ensure that the number of total threads is not set to be much larger than the maximum number of simultaneous requests expected for the server.

Open threads

Indicates the number of threads that were opened on the database during the last measurement period.

Number

 

Thread usage

Indicates the percentage of threads that were in use during the last measurement period.

Percent