Welcome to this week’s Planets9s, covering all the latest resources and technologies we create around automation and management of open source database infrastructures.

In this blog, I provide answers to the Q & A for the Troubleshooting hardware resource usage webinar.

First, I want to thank everybody who attended the May 26 webinar. The recording and slides for the webinar are available here. Below is the list of your questions that I wasn’t able to answer during the webinar, with responses:

Q: How did you find the memory IO LEAK?

A: Do you mean the replication bug I was talking about in the webinar? I wrote about this bug …

Thanks to everyone who participated in this week’s popular webinar on MySQL Database Performance Tuning, which looked at answering the following questions:

• You’re running MySQL as backend database, how do you tune it to make best use of the hardware?
• How do you optimize the Operating System?
• How do you best configure MySQL for a specific database workload?

The replay of this webinar is now available online:

Watch the replay

In this webinar, Krzysztof Książek, Senior Support Engineer at Severalnines, discussed some of the settings that are most often tweaked and which can bring you significant improvement in the performance of your MySQL database. Krzysztof  also covered some of the variables which are frequently modified even though they …

Last week during the Oracle Users Group Leaders Summit in Bucharest I had the pleasure the meet the leaders for the MySQL Users Group from Azerbaijan,  Finland, Madrid and the Netherlands.

During some discussions, it appeared that some users are not aware of the Performance_Schema integration in MySQL Workbench. Indeed with WB you can enable PFS, add sys table if not present by default (<5.7).

You can use a default configuration or customize it and enable all the instruments and consumers you need.

When enabled, you can generate some useful reports

In case you are also not yet aware of it, the following dashboard is also available in MySQL Workbench

The latest version of MySQL Workbench has been released yesterday, June 13th : 6.3.7 GA

If you require to get all the records of current year using mysql query for example you have one table items and columns are id title description createdat and updateat Now you want to get all records of this year so you can fetch fields value using DATESUB and INTERVAL of mysql In follo

If you require to get all the records of current year using mysql query for example you have one table items and columns are id title description createdat and updateat Now you want to get all records of this year so you can fetch fields value using DATESUB and INTERVAL of mysql In follo

In this post, we’ll look at scaling Percona XtraDB Cluster with ProxySQL in Docker Swarm.

In my previous post, I showed how to employ Percona XtraDB Cluster on multiple nodes in a Docker network.

The intention is to be able to start/stop nodes and increase/decrease the cluster size dynamically. This means that we should track running nodes, but also to have an easy way to connect to the cluster.

So there are two components we need: service discovery to register nodes and ProxySQL to handle incoming traffic.

The work with service discovery is already bundled with Percona …

MySQL 5.7 has been GA since October 2015. At the time of writing, it is still a very new release. But more and more companies are looking into upgrading, as it has a list of great new features. Schema changes can be performed with less downtime, with more online configuration options. Multi-source and parallel replication improvements make replication more flexible and scalable. Native support for JSON data type allows for storage, search and manipulation of schema-less data.

An upgrade, however, is a complex process - no matter which major MySQL version you are upgrading to. There are a few things you need to keep in mind when planning this, such as important changes between versions 5.6 and 5.7 as well as detailed testing that needs to precede any upgrade process. This is especially important if you would like to maintain availability for the duration of the upgrade.

…

As Morgan announced it his blog post related to new defaults in 5.7, in 5.7.7 and newer the default value of sync_binlog is now 1.

This of course has an impact on performance especially if you don’t have fast storage like a RAID controller with a cache for example.

Already in O’reilly High Performance MySQL, is was written that the most important setting for binary logging on the master is sync_binlog = 1.

And this recommendation was made for MySQL 5.0 ! At that time the performance impact could reach 50%. In 5.6, with the addition of binary log group commit …

The MySQL developer tools team announces 6.3.7 as our GA release for MySQL Workbench 6.3. 

For the full list of changes in this revision, visit 
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html 

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/list.php?152

Download MySQL Workbench 6.3.7 GA now, for Windows, Mac OS X 10.9+, 
Oracle Linux 6 and 7, Fedora 23 and Fedora 24, Ubuntu 16.04 or sources, from:

http://dev.mysql.com/downloads/tools/workbench/ 

Enjoy!