Few days ago I came across the announcement that MaxScale 1.3 finally supports Persistent Connection.
ProxySQL supports persistent connection since it was a prototype (sometime back in 2013), therefore I am very happy that the MaxScale Team finally introduced a long waited feature.
Although, MaxScale implementation of persistent connection has a serious drawback and I would consider it as a serious bug (more details at the end of the article). A bug so serious that shouldn't reach any GA release.

Since I like running benchmark, and due the new feature in MaxScale, I thought it is a good time to compare again ProxySQL vs MaxScale, around 6 months after a previous benchmark .

Benchmark : ProxySQL vs MaxScale
Benchmark …

jjs is a JavaScript shell that ships with Oracle Java 1.8. I recently found myself in a situation where it seemed worth while to check it out, so I did. I do not want to use this post to elaborate too much on why I started looking at jjs, but I intend to write about that shortly. For now I just want to share a few observations, as well as a solution to a particular obstacle I encountered. What is jjs?Java 1.8 (both SDK and JRE) ships a new executable called …

Another post in the EXPLAIN FORMAT=JSON is Cool! series! In this post, we’ll discuss how the EXPLAIN FORMAT=JSON provides optimization details for 

ORDER BY

 and  

GROUP BY

 operations in conjunction with 

order_by_subqueries

 and  

group_by_subqueries

. 

EXPLAIN FORMAT=JSON

 can print details on how a subquery in

ORDER BY

 is optimized:

mysql> explain format=json select emp_no, concat(first_name, ' ', last_name) f2 from employees order by (select emp_no limit 1)G
*************************** 1. row ***************************
EXPLAIN: { …

One of the most common engagements I do is working with firms in and around the NYC startup sector. I evaluate AWS infrastructures & applications built in the Amazon cloud. Join 32,000 others and follow Sean Hull on twitter @hullsean. I’ve seen some patterns in customers usage of Amazon. Below is a laundry list of … Continue reading 5 core pieces of the Amazon Cloud puzzle to get your project off the ground → …

InnoDB and the Thread Sanitizer do not work well together in MySQL 5.7.  There are hundreds of possible data races reported by the Thread Sanitizer in the InnoDB code for the simplest case of initializing the MySQL server and shutting it down.  Luckily, most of these data races are benign.  The problem of finding an interesting data race in the InnoDB software is similar to finding evidence of a sub-atomic particle in a particle accelerator; many Thread Sanitizer events must be analyzed before something interesting is found.

One example of a benign data race is InnoDB's implementation of fuzzy counters.  A …

MySQL 5.7 comes with enhancements which makes a deployment secure by default. These features try to minimize attack surface as much as possible without hampering usability aspect. They are useful for novice user because they help close common security loopholes which can be leveraged by an attacker.…

Ahoi, I made three proposals for Percona Live. (Even I know being a lonely (sniff) freelancer with no backup).  At least I'm for sure an early adopter about the three topics I submitted and know for sure what I'm talking about *g*   

• Using Ansible to Deploy MySQL

Even being Puppet certified. Ansible is my love. Never been that fast in doing automation \o/

• Dockerize it/IT

This is a tutorial about Docker and Galera/MySQL. 

• Docker …

A few days ago I came across the announcement that MaxScale 1.3 finally supports Persistent Connection.

ProxySQL has supported Persistent Connection since it was a prototype (sometime back in 2013). I am therefore very happy that the MaxScale Team finally introduced a long awaited feature.

However, MaxScale's implementation has a serious drawback and I consider it a serious bug (more details towards the end of the article). A bug so serious that it shouldn't reach any GA release.

I like running benchmarks, and given the new feature in MaxScale, I thought it a good time to compare ProxySQL vs MaxScale again. It's been around 6 months since the previous benchmark.

ProxySQL vs MaxScale Benchmark setup

The benchmark setup is very simple:

• a physical server (20 CPU cores) running sysbench, proxysql and maxscale
• a physical server (20 CPU cores) running 3 mysqld …

A few days ago I came across the announcement that MaxScale 1.3 finally supports Persistent Connection.

ProxySQL has supported Persistent Connection since it was a prototype (sometime back in 2013). I am therefore very happy that the MaxScale Team finally introduced a long awaited feature.

However, MaxScale's implementation has a serious drawback and I consider it a serious bug (more details towards the end of the article). A bug so serious that it shouldn't reach any GA release.

I like running benchmarks, and given the new feature in MaxScale, I thought it a good time to compare ProxySQL vs MaxScale again. It's been around 6 months since the previous benchmark.

ProxySQL vs MaxScale Benchmark setup

The benchmark setup is very simple:

• a physical server (20 CPU cores) running sysbench, proxysql and maxscale
• a physical server (20 CPU cores) running 3 mysqld …

The previous post in the EXPLAIN FORMAT=JSON is Cool! series showed an example of the query

select dept_name from departments where dept_no in (select dept_no from dept_manager where to_date is not null)

, where the subquery was materialized into a temporary table and then joined with the outer query. This is known as a semi-join optimization. But what happens if we turn off this optimization?

EXPLAIN FORMAT=JSON

 can help us with this investigation too. …