Created MySQL Scripts Repository

Most of my work is with Oracle databases but I have been starting to learn a little bit about MySQL. Where I work, we have a bunch of on premises Oracle databases including large and active ones with various challenging performance tuning problems that I enjoy working on. But for the last couple or so years we have been using MySQL on RDS within Amazon’s cloud (AWS). I have not had many chances to work on a MySQL performance issue, but I want to be ready when the time comes. Back in 2019 I read several chapters of the MySQL 5.7 reference manual and started looking at tuning. Last week I picked it up again. I was mainly looking at Amazon’s Performance Insights that we have running on our RDS databases and seeing what information it gave us and how to link that back to other tables/views that MySQL uses for performance. Anyway, I have made notes on our internal web pages, but I also decided to create a public GitHub repository with some of the SQL and Python scripts that I have created so far. It is very basic, and I am sure that other people have more sophisticated tools, but I think it is helpful to me to create the repository and to update it as I learn more. So, if you are interested here it is:


About Bobby

I live in Chandler, Arizona with my wife and three daughters. I work for US Foods, the second largest food distribution company in the United States. I have worked in the Information Technology field since 1989. I have a passion for Oracle database performance tuning because I enjoy challenging technical problems that require an understanding of computer science. I enjoy communicating with people about my work.
This entry was posted in Uncategorized. Bookmark the permalink.

2 Responses to Created MySQL Scripts Repository

  1. Sai says:

    Hi Bobby,

    I find your information on MySQL is very helpful. What are your thoughts on turning performance schema on Production environment?


    • Bobby says:


      I am new to MySQL tuning so I am still learning, but it seems like you can turn performance schema on and off pretty easily and that you can pick and choose which parts to leave on. I have not done any testing to see which features cause the most overhead and use the most disk space but I know that you can leave some of the features turned on without a problem. AWS’s Performance Insights requires certain performance schema features to be turned on ( and so we have these in place now in production without issue. But there are a lot more features that we have turned off so I cannot say from experience about them.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.