Aurimas Mikalauskas, Author at Percona Database Performance Blog

Hyper-threading – how does it double CPU throughput?

Aurimas Mikalauskas | January 15, 2015 | Posted In: Benchmarks, Insight for DBAs, MySQL

The other day a customer asked me to do capacity planning for their web server farm. I was looking at the CPU graph for one of the web servers that had Hyper-threading switched ON and thought to myself: “This must be quite a misleading graph – it shows 30% CPU usage. It can’t really be […]

Optimizing MySQL for Zabbix

Aurimas Mikalauskas | November 14, 2014 | Posted In: High-availability, InnoDB, MySQL

This blog post was inspired by my visit at the annual Zabbix Conference in Riga, Latvia this year, where I gave a couple of talks on MySQL and beyond. It was a two day single-track event with some 200 participants, a number of interesting talks on Zabbix (and related technologies) and really well-organized evening activities. […]

Here’s my favorite secret MySQL 5.6 feature. What’s yours?

Aurimas Mikalauskas | September 5, 2013 | Posted In: MySQL

MySQL 5.6 has a great many new features, including, but certainly not limited to a number of performance improvements. However, besides the widely talked-about features such as InnoDB support for full text search, optimizer, performance schema improvements and GTID, there are also a few tiny improvements that nobody cared to mention. One such feature is…

Sphinx search performance optimization: multi-threaded search

Aurimas Mikalauskas | January 16, 2013 | Posted In: MySQL

Queries in MySQL, Sphinx and many other database or search engines are typically single-threaded. That is when you issue a single query on your brand new r910 with 32 CPU cores and 16 disks, the maximum that is going to be used to process this query at any given point is 1 CPU core and […]

Sphinx search performance optimization: attribute-based filters

Aurimas Mikalauskas | January 15, 2013 | Posted In: Insight for Developers, MySQL

One of the most common causes of a poor Sphinx search performance I find our customers face is misuse of search filters. In this article I will cover how Sphinx attributes (which are normally used for filtering) work, when they are a good idea to use and what to do when they are not, but […]

How does MySQL Replication really work?

Aurimas Mikalauskas | January 9, 2013 | Posted In: Insight for DBAs, MySQL, Replication

While we do have many blog posts on replication on our blog, such as on replication being single-threaded, on semi-synchronous replication or on estimating replication capacity, I don’t think we have one that covers the very basics of how MySQL replication really works on the high level. Or it’s been so long ago I can’t […]

How to STOP SLAVE on Amazon RDS read replica

Aurimas Mikalauskas | December 20, 2012 | Posted In: Cloud and MySQL, Cloud and NoSQL, Insight for DBAs, MySQL

We are doing a migration from Amazon RDS to EC2 with a customer. This, unfortunately, involves some downtime – if you are an RDS user, you probably know you can’t replicate an RDS instance to an external server (or even EC2). While it is annoying, this post isn’t going to be a rant on how […]

Is Replication Slave ever going to catch up? When?!

Aurimas Mikalauskas | August 29, 2012 | Posted In: Insight for DBAs, MySQL

If you ever had a replication slave that is severely behind, you probably noticed that it’s not catching up with a busy master at a steady pace. Instead, the “Seconds behind master” is going up and down so you can’t really tell whether the replica is catching up or not by looking at just few […]

Sell-an-Elephant-to-your-Boss-HOWTO

Aurimas Mikalauskas | August 28, 2012 | Posted In: Insight for DBAs, Insight for Developers

Spoiler alert: If your boss does not need an elephant, he is definitely NOT going to buy one from you. If he will, he will regret it and eventually you will too. I must appologize to the reader who was expecting to find an advice on selling useless goods to his boss. While I do […]

Binary log file size matters (sometimes)

Aurimas Mikalauskas | May 24, 2012 | Posted In: Insight for DBAs, MySQL

I used to think one should never look at max_binlog_size, however last year I had a couple of interesting cases which showed that sometimes it may be very important variable to tune properly. I meant to write about it earlier but never really had a chance to do it. I have it now!

Hyper-threading – how does it double CPU throughput?

Optimizing MySQL for Zabbix

Here’s my favorite secret MySQL 5.6 feature. What’s yours?

Sphinx search performance optimization: multi-threaded search

Sphinx search performance optimization: attribute-based filters

How does MySQL Replication really work?

How to STOP SLAVE on Amazon RDS read replica

Is Replication Slave ever going to catch up? When?!

Sell-an-Elephant-to-your-Boss-HOWTO

Binary log file size matters (sometimes)

Upcoming Webinars

PERCONA

SERVICES

SOFTWARE

RESOURCES

CONTACT US

COMMUNITY

CONFERENCES

ABOUT