Configuration of MySQLWorkLdTest

A resource-hungry or a long-running query is one of the main reasons for performance degradation of the target database server instance. When such queries execute on the server, they hog almost all the available 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 target MySQL database server at all times, such queries should be rapidly identified and quickly optimized to minimize resource usage. This is where the MySQLWorkLdTest test helps.

At configured intervals, this test reports the maximum number of internal on-disk temporary tables created by the server while executing statements. This test also reports how long did a query take for execution and how long did a query spend waiting for table locks. In addition, this test also throws light on the count of table scans that happened on the database server instance. Using the detailed diagnostics of this test, administrators can figure out inefficient queries and proceed to optimize them to enhance server performance.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to choose how often should the test be executed.

• In the HOST text box, specify the IP address of the host for which the test is to be configured.

• In the PORT text box, specify the port at which the specified host listens.

• In the DATABASE text box specify the name of a database on the target MySQL database server being monitored.

• 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. Specify the credentials of such a user in the USERNAME and PASSWORD text boxes. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server topic in the Monitoring MySQL Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• The DETAILED DIAGNOSIS makes 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:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.