MySQL Group Replication is a hot topic in MySQL ecosystem.
We have been evaluating it in , and it is now time to evaluate its performance, especially now that is GA.
In our setup, we wanted to evaluate how it performs compared to standard asynchronous MySQL replication. Therefore MySQL 5.7.17 was first tested with regular async replication, MTS, semi-sync, and finally Group Replication.

Setup

The first testing environment is a 3 nodes "cluster", with 1 master and 2 async slaves in the same network.
Each node has Intel Xeon CPU E5-2660 v2 @ 2.20GHz , 20 cores.

For benchmark we used sysbench running on a 4th node, using a database with 8 tables with 10M rows each, therefore the dataset completely fits in memory.
sysbench was executed as:

./sysbench --num-threads=64 --max-time=300 --max-requests=0 --test=./lua/oltp_update_index.lua --mysql-user=sbtest --mysql-password=sbtest …

MySQL Group Replication is a hot topic in MySQL ecosystem.
We have been evaluating it in , and it is now time to evaluate its performance, especially now that is GA.
In our setup, we wanted to evaluate how it performs compared to standard asynchronous MySQL replication. Therefore MySQL 5.7.17 was first tested with regular async replication, MTS, semi-sync, and finally Group Replication.

Setup

The first testing environment is a 3 nodes "cluster", with 1 master and 2 async slaves in the same network.
Each node has Intel Xeon CPU E5-2660 v2 @ 2.20GHz , 20 cores.

For benchmark we used sysbench running on a 4th node, using a database with 8 tables with 10M rows each, therefore the dataset completely fits in memory.
sysbench was executed as:

./sysbench --num-threads=64 --max-time=300 --max-requests=0 --test=./lua/oltp_update_index.lua --mysql-user=sbtest --mysql-password=sbtest …

In this blog, we’ll discuss how to use concurrency to help with WAN latency when using synchronous clusters.

WAN Latency Problem

Our customers often ask us for help or advice with WAN clustering problems. Historically, the usual solution for MySQL WAN deployments is having the primary site in one data center, and stand-by backup site in another data center (replicating from the primary asynchronously). These days, however, there is a huge desire to employ available synchronous replication solutions for MySQL. These solutions include things like Galera (i.e., Percona XtraDB Cluster) or the recently released MySQL Group Replication. This trend is attributable to the fact that these solutions are less problematic and provide more automatic fail over and fail back procedures. But it’s also because businesses want to write in both data centers simultaneously.

Unfortunately, WAN link reliability and latency makes …

Percona announces the release of Percona Server for MySQL 5.5.54-38.6 on February 1, 2017. Based on MySQL 5.5.54, including all the bug fixes in it, Percona Server for MySQL 5.5.54-38.6 is now the current stable release in the 5.5 series.

Percona Server for MySQL is open-source and free. You can find release details in the 5.5.54-38.6 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.

…

The FOSDEM MySQL & Friends Community Dinner 2017 is sold out. In the first 24 hours of opening up the registration for the dinner, we sold more than 40 of the 63 total tickets!

I quickly wanted to take some time again to thank our sponsors, who help keep this event possible and affordable:

Wondering how to get there from Fosdem?

The venue itself is located very close to the VUB. You can find the route to get there  …

Introduction

Now that Galera Cluster 5.7 GA has been released, let’s take a look at some features in MySQL 5.7 that improve Galera performance or allow new workloads and applications to be Galera-enabled.

Spatial indexes come to InnoDB and Galera

Previously, only MyISAM tables could have indexes on spatial columns. Starting with 5.7, it is now possible to use spatial indexes with InnoDB tables as well. This way applications in the areas of GIS, geo-location, mapping, etc. can take advantage of Galera replication for their spatial data.

CREATE TABLE geometry_table (
    geometry_column GEOMETRY NOT NULL,
    SPATIAL INDEX(geometry_column)
) ENGINE=InnoDB;

It is also possible to migrate existing spatial data stored in MyISAM or replicated using traditional asynchronous replication to InnoDB and Galera.

JSON support

If you have previously considered using another database …

I will be heading to Brussels on Friday for FOSDEM.

On Friday, February 3rd, I will attend the Pre-FOSDEM MySQL Day where I will give two talks:

How Booking.com avoids and deals with replication lag (at 12:05), Monitoring Booking.com without looking at MySQL (at 15:30).

(A summary of those talks can be found in Le Fred's blog.)

Then, on Saturday, February 4th, I have a talk in the MySQL

Three ways to schedule a MySQL query

If you walk through any office you see people working in Excel. With MySQL for Excel (https://www.mysql.com/why-mysql/windows/excel/) you can already let them pull information from Excel themselves. However, in some cases it saves a lot of time if they don’t have to pull the information, but it’s pushed automatically.
Exception lists are the best examples of queries you want to push to users. If you have a query with occasional results, you don’t want to check for this every day. In this case you just want to receive a mail if there are any results. Eg a list of stuck invoices which can’t be processed automatically.
How can we do this?

1. Using the MySQL Event Scheduler

The MySQL Event scheduler can be used to run a query on a predefined schedule and output the results in CSV format. …

Sometimes we are not sure if the database design we have created and our site has been using is correct and optimised. We all do have this feeling at times don't we :)


Well, MySQL provides with PROCEDURE ANALYSE() to help us detect inconsistencies in our database design by suggesting for an optimal datatype and data length for columns.

The syntax for using PROCEDURE ANALYSE() is as below:

SELECT ... FROM ... WHERE ... PROCEDURE
ANALYSE([max_elements,[max_memory]])

Ref: …

In this blog post, I’ll discuss MySQL sharding models, and how they apply to SaaS application environments.

MySQL is one of the most popular database technologies used to build many modern SaaS applications, ranging from simple productivity tools to business-critical applications for the financial and healthcare industries.

Pretty much any large scale SaaS application powered by MySQL uses sharding to scale. In this blog post, we will discuss sharding choices as they apply to these kinds of applications.

In MySQL, unlike in some more modern technologies such as MongoDB, there is no standard sharding implementation that the vast majority of applications …