ProxySQL brings a lot of value to your MySQL infrastructures such as Caching or Connection Multiplexing but it does not come free — your database needs to go through additional processing traffic which adds some overhead. In this blog post, we’re going to discuss where this overhead comes from and measure such overhead. 

Types of Overhead and Where it Comes From 

There are two main types of overhead to consider when it comes to ProxySQL — Network Overhead and Processing Overhead. 

Network Overhead largely depends on where you locate ProxySQL. For example, in case you deploy ProxySQL on the separate host (or hosts) as in this diagram: 

The application will have added network latency for all requests, compared to …

Owing to the success and feedback we received from our last training course, we will be running another 2 sessions, both for European, as we well as Pacific Time zones

Delivered by our Professional ProxySQL Trainers who have built and actively maintain ProxySQL.

ProxySQL was built in order to help build, support and improve MySQL infrastructure.

Our public 2x Day Training course will help you learn about how to use ProxySQL’s features effectively and to efficiently deal with real life events and emergency situations in your infrastructure.

The rich course content provides insights to help you build a strong understanding of the tool’s design goals, and most importantly… how to properly implement ProxySQL in order to maximize the resource utilization of your database cluster while avoiding common pitfalls and anti-patterns!

Immerse yourself in the world of ProxySQL with our two-day …

ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.13 on the 15th of July 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

New Features

Although only bug fixes are supposed to go into ProxySQL 2.0, we had to introduce a few minor new features:

• A client can force ProxySQL to run a query in a new connection using a query annotation using create_new_connection=1 in a comment. For example SELECT /* create_new_connection=1 */ 1 . See #2874
• Added …

We’re very excited to open up our ProxySQL Total Training online course to the public!

Get yourself, or your team, trained by our Professional ProxySQL Trainers who have built and actively maintain ProxySQL in our upcoming total Training course.

Designed for DBAs, application developers and IT professionals in the industry, the course will focus on real world implementation and hands-on labs that will ensure you acquire the needed skills to deploy efficient, scalable and highly available solutions with ProxySQL!

Immerse yourself in the world of ProxySQL with our two-day ProxySQL Total Training.

ProxySQL Total Training topics include:

• ProxySQL use cases and real world examples
• How to install, upgrade and configure ProxySQL with zero-downtime
• Query routing, query caching and query fire-walling
• Advanced performance …

ProxySQL Firewall Overview

ProxySQL’s flexible query rules engine has many uses, from Read/Write splitting, sharding and even creating firewall blacklist. This allows ProxySQL to be loved by both Performance and Security-minded engineers.

Starting in ProxySQL 2.0.9, ProxySQL has another Security feature: the Firewall Whitelist.

Modeled on MySQL Enterprise Firewall, this allows a security-conscious administrator to tune access to only allow certain queries.

Imagine a situation where your webapp gets hacked, which exposes your user’s database credentials.

If your webapp connects directly to the database, the malicious user can do what they want to your data with the same permissions your webapp has.

So perhaps they can’t just DROP TABLE because you’ve smartly removed DDL permissions …

The Percona Kubernetes Operator for Percona XtraDB Cluster(PXC) comes with ProxySQL as part of the deal. And to be honest, the behavior of ProxySQL is pretty much the same as in a regular non-k8s deployment of it. So why bother to write a blog about it? Because what happens around ProxySQL in the context of the operator is actually interesting.

ProxySQL is deployed on its own POD (that can be scaled as well as the PXC Pods can). Each ProxySQL Pod has its own ProxySQL Container and a sidecar container. If you are curious, you can find out which node holds the pod by running

kubectl describe pod cluster1-proxysql-0 | grep Node:
Node: ip-192-168-37-111.ec2.internal/192.168.37.111

Login into and ask for the running containers. You will see something like this:

[root@ip-192-168-37-111 ~]# docker ps | grep -i proxysql …

In real life, there are frequent cases where getting a running application to work correctly is strongly dependent on consistent write/read operations. This is no issue when using a single data node as a provider, but it becomes more concerning and challenging when adding additional nodes for high availability and/or read scaling. 

In the MySQL dimension, I have already described it here in my blog Dirty Reads in High Availability Solution.

We go from the most loosely-coupled database clusters with primary-replica async replication, to the fully tightly-coupled database clusters with NDB Cluster (MySQL/Oracle).

Adding components like ProxySQL to the architecture can, from one side, help in improving high availability, and from the other, it can amplify and randomize the negative effect of …

Long months of the pandemic lockdown have brought to life many great online events enabling the MySQL community to get together and stay informed about the very recent developments and innovations available to MySQL users. It isn’t over yet! Next Thursday, June 4th, Percona & ProxySQL are co-hosting the ProxySQL Tech Talks with Percona virtual meetup covering ProxySQL, MySQL and Percona XtraDB Cluster.

The attendees are invited to participate in the two-hour deep-dive event with plenty of time for questions and answers (we will have two 40-minute sessions + 20 minutes allocated for Q&A). Get prepared, come with your burning questions and true war stories – we’ll have our speakers answer and comment on them! And here come the speakers:

• René Cannaò, ProxySQL author and CEO of ProxySQL …

ProxySQL is proud to announce the fast track release of the latest stable version of ProxySQL 2.0.12 on 18th of May 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights Enhancements

• Added tracking capability for variable group_concat_max_len #2709
• Do not compile if GIT_VERSION is not set #2768
• Several new automated …

In this blog post I would like to give an overview of the most common failover scenarios and operations when using MySQL Group Replication 8.0.19 (aka GR) and Percona XtraDB Cluster 8 (PXC) (which is based on Galera), and explain how each technology handles each situation. I have created a three-node cluster with Group Replication using a single Primary and a three-node PXC, both with default settings. I am also going to use ProxySQL to interface with both clusters.

In both clusters, the name of the nodes are mysql1, mysql2,  and mysql3. In Group Replication the Primary node is where the writes go if we are using single primary configuration. In PXC, I will use the same term as well and will call the node Primary where I am sending the writes. Just to note, in PXC there is no concept of primary node, …