Solving Performance Problems Using MySQL Enterprise Monitor

Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |
Solving Performance Problems
Using MySQL Enterprise Monitor
Mark Matthews
Consulting Member, Technical Staff - Oracle
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.

Agenda
• Creating a test Group Replication cluster
• Monitoring the cluster
• Diagnosing performance problems using MySQL Enterprise Monitor’s Query Analyzer
• Diagnosing performance problems using MySQL Enterprise Monitor events
• Diagnosing availability problems with Group Replication
The examples used in this presentation were developed with MySQL-5.7 and Enterprise Monitor
3.4.

Creating a 3-Node Group Replication Cluster
[mem@localhost]$ mysqlsh
In a terminal window, start the MySQL Shell:

mysql-js> dba.deploySandboxInstance(3310)
A new MySQL sandbox instance will be created on this host in /home/mem/mysql-
sandboxes/3310
Please enter a MySQL root password for the new instance: (use mysql)
Deploying new MySQL instance...Instance localhost:3310 successfully deployed and started.
Use shell.connect('root@localhost:3310'); to connect to the instance.
Create sandbox instances – one on port 3310 (1/3)

sandboxes/3311

sandboxes/3312

mysql-js> connect root@localhost:3310
Creating a Session to 'root@localhost:3310'
Enter password:
Your MySQL connection id is 286
Server version: 5.7.19-log MySQL Community Server (GPL)
No default schema selected; type use <schema> to set one.
Create cluster using just-created sandbox nodes

mysql-js> var cluster = dba.createCluster(’my_cluster')
A new InnoDB cluster will be created on instance 'root@localhost:3310'.
Creating InnoDB cluster ’my_cluster' on 'root@localhost:3310'...
Adding Seed Instance...
Cluster successfully created.
Use Cluster.addInstance() to add MySQL instances.
At least 3 instances are needed for the cluster to be able to withstand up to one server failure.
Create a group replication cluster using just-created sandbox nodes

mysql-js> cluster.addInstance('root@localhost:3311')
A new instance will be added to the InnoDB cluster. Depending on the amount of
data on the cluster this might take from a few seconds to several hours.
Please provide the password for 'root@localhost:3311': (use mysql)
Adding instance to the cluster ...
The instance 'root@localhost:3311' was successfully added to the cluster.
Add node 3311 to the cluster

Please provide the password for 'root@localhost:3312': (use mysql)
Adding instance to the cluster ...
The instance 'root@localhost:3312' was successfully added to the cluster.
Add node 3312 to the cluster

Download the Sakila Sample Database
https://dev.mysql.com/doc/index-other.html

Install the Sakila Database Schema and Data
[mem@localhost mysql-sandboxes]$ mysql -uroot -pmysql --port=3310 -- host=127.0.0.1
mysql> source [path-to-sakila-files]/sakila-schema.sql
mysql> source [path-to-sakila-files]/sakila-data.sql
In a new terminal window

Issue some problematic queries
mysql> SELECT * FROM film WHERE EXISTS(SELECT * FROM film_actor WHERE
actor_id=1 AND film_actor.film_id = film.film_id);
mysql> SELECT rental_rate, release_year FROM film WHERE rental_rate=4.99 ORDER BY
release_year;
In the mysql command line client:

Issue some problematic queries
[mem@localhost]$ for i in {1..100}; do mysql -uroot -pmysql -e "SELECT * FROM category";
done
In a shell window – execute some simple, repeated queries

Authenticate to the Service Manager and Monitor Targets

Observing Discovery of Monitored Targets

Replication Topology View for Group Replication

Finding Query Performance Issues Using Query Analyzer

Performance Issue #1 - Queries with Quasi-Static Results

Performance Issue #2 - Queries with Full Table Scans

Performance Issue #2 – Dependent Subquery
SELECT * FROM film WHERE EXISTS(SELECT *
FROM film_actor WHERE actor_id=1 AND
film_actor.film_id = film.film_id)
SELECT film.* FROM sakila.film INNER JOIN
sakila.film_actor USING (film_id) WHERE
actor_id = 1

Performance Issue #3 - Queries Causing File Sorts

Automated Performance Issue Detection

Performance Issue #4 – Long-Running Queries

Performance Issue #5 – Table Cache Size Incorrect

Bonus Performance Issue – Replication Outages
mysql-js> dba.killSandboxInstance('root@localhost:3312')

Bonus Performance Issue – Replication Outages

Replication Outages – Repair The Loss of Quorum
sandboxes/3311
Deploying new MySQL instance...
Instance localhost:3314 successfully deployed and started.

Replication Outages – Repair The Loss of a Node
sandboxes/3311
Deploying new MySQL instance...
Instance localhost:3314 successfully deployed and started.

Bonus Performance Issue – Node Added (not Monitored)

Bonus Performance Issue – Node Added (Monitored)

How Do I Get it?
• MySQL Enterprise Monitor is included with Oracle MySQL Enterprise Edition:
• Support
• MySQL Enterprise Backup
• MySQL Enterprise Audit
• MySQL Enterprise Firewall
• MySQL Enterprise Scalability
• MySQL Enterprise Transparent Data Encryption
• MySQL Enterprise Authentication
• Trials available at http://edelivery.oracle.com/

Questions?

Thank You!

Solving Performance Problems Using MySQL Enterprise Monitor

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Solving Performance Problems Using MySQL Enterprise Monitor

Similar to Solving Performance Problems Using MySQL Enterprise Monitor (20)

More from OracleMySQL

More from OracleMySQL (6)

Recently uploaded

Recently uploaded (20)

Solving Performance Problems Using MySQL Enterprise Monitor