Today I delivered a session related on what is MySQL implementing to take the make the devops life easier.

You can find the slides below:

Thanks to everyone who participated in this week’s webinar on working with optimizer and SQL tuning. In this session, Krzysztof Książek, Senior Support Engineer at Severalnines, discussed how execution plans are calculated. He also took a closer look at InnoDB statistics, how to hint the optimizer and finally, how to optimize SQL.

Watch the replay

The complete MySQL Query Tuning Trilogy is available to watch online, so if you missed the first two parts, you can now catch up with them on demand.

MySQL Query Tuning Trilogy

An in-depth look into the ins and outs of optimising MySQL queries

When done right, tuning MySQL queries and indexes can significantly increase the performance of your application as well as decrease response times. This is why we’ve covered this complex …

MySQL 8.0 has a new feature called “invisible indexes,” which allow you to quickly enable/disable indexes from being used by the MySQL Optimizer.

I wanted to share some of my first experiences and thoughts about this new feature.

Why is it good for us?

There are a couple of use cases. One of them is if you want to drop an index, but want to know the effect beforehand. You can make it invisible to the optimizer. It is a quick metadata change to make an index invisible. Once you are sure there is no performance degradation, you can then drop the index.

The main point is that the invisible index is unavailable for use by the optimizer, but it is still present and kept up-to-date by write operations. The optimizer won’t use it, even if we try to “FORCE INDEX”. I think we should be …

Starting with MySQL 8.0, we will drop libmysqld (aka “embedded server”). This change will affect only a handful of users, but for context let me start with an introduction.

Introduction

libmysqld (also referred to as “the embedded server”) is a way of using MySQL without the client server protocol.…

Does InnoDB page size matter? janlindstrom Wed, 10/26/2016 - 23:44

From MariaDB 10.1 there is a feature where the InnoDB page size can be configured to be larger than the default 16K for normal, uncompressed tables. However, there has been little performance results that show whether the page size really effects  the transaction performance or response time. In this blog, we study effects of page size on three different storage devices using the same benchmark(s). These devices are:

• Traditional hard disk
• SSD (Tree Intel X25-E Extreme SSDSA2SH032 G1GN 2.5-inch 32GB SATA II SLC Internal Solid State Drive as RAID-0)
• FusionIO NVM device (ioMemory SX300-1600 with VSL driver 4.2.1 build 1137 and NVMFS 1.1.1)

Results from different devices should not be compared to each other, as there are other variables like device bandwidth and different file systems. Instead, we will look at page …

In previous blog posts we explained how to perform certain actions in a MySQL database set up as a document store using Connector/Node.js. In this blog post we are going to use some of the examples covered to explain how to start working with an application created with Express.js, AngularJS, Node.js, and MySQL Connector/Node.js.

Required

• Node.js
• Express.js
• AngularJS
• MySQL Connector/Node.js
• MySQL Server 5.7.12 or higher

Optional

• …

A quick look at ProxySQL

There is a lot of buzz in the MySQL community around ProxySQL, an open-source SQL-aware proxy. I was lucky enough to give a ProxySQL Tutorial at PerconaLive Amsterdam 2016 with the creator of ProxySQL, René Cannaò.

Some of ProxySQL’s features include:

• Query rules based on Google’s RE2-style regex
• Failover detection
• Connection multiplexing

ProxySQL’s approach to implementing regex-style query rules opens the door to some pretty fascinating possibilities. Just to name a few examples:

• Read/write splitting between the write master and read slaves
• Query firewall, for those times you wish you could prevent queries from hitting the database. Perhaps you are …

Dear MySQL users,

MySQL Connector/Python 2.0.5 GA is a new GA version of 2.0 release series of the pure Python database driver for MySQL. It can be used for production environments.

MySQL Connector/Python version 2.0.5 is compatible with MySQL Server versions 5.5 and greater. Python 2.6 and greater as well as Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2 are not supported.

MySQL Connector/Python 2.0.5 is available for download from:
http://dev.mysql.com/downloads/connector/python/#downloads

The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 2.0.5. For a more complete list of changes, see below or online at:
http://dev.mysql.com/doc/relnotes/connector-python/en/

Changes in MySQL Connector/Python 2.0.5 (2016-10-26)

Bugs Fixed

* A potential SQL injection vector was eliminated. (Bug #22529828, …

In our current project the customer wants to install and run multiple MySQL Enterprise Server 5.7 Instances on the same machine (yes, I know about virtualization (we run on kvm), containers, Docker, etc.). He wants to use Red Hat Enterprise Linux (RHEL) 7 which brings the additional challenge of SystemD. So mysqld_multi is NOT an option any more.

We studied the MySQL documentation about the topic: Configuring Multiple MySQL Instances Using systemd. But to be honest: It was not really clear to me how to do the job...

So we started to work out our own cook-book which I want to share here.

The requirements are as follows:

• Only ONE version of MySQL Enterprise Server binaries at a time is available. If you want to have more complicated set-ups (multi version) consider our …

Take Percona’s poll on what database technologies you use in your environment.

Different databases get designed for different scenarios. Using one database technology for every situation doesn’t make sense, and can lead to non-optimal solutions for common issues. Big data and IoT applications, high availability, secure backups, security, cloud vs. on-premises deployment: each have a set of requirements that might need a special technology. Relational, document-based, key-value, graphical, column family – there are many options for many problems. More and more, database environments combine more than one solution to address the various needs of an enterprise or application (known as polyglot persistence).

Please take a few seconds and answer the following poll on database technologies. Which are you using? Help …