May 24, 2012

Post: How to Monitor MySQL with Percona's Nagios Plugins

can cause two serious types of problems: the disk can fill up with no apparent cause or solution, or you can restart the servermany init scripts will behave very badly. Sample problems include starting two instances of MySQL on the same files in

Post: How Percona does a MySQL Performance Audit

in terms of size and spindle speed. I need to know how many physical spindles are under the box, and how fast they are. I canyou‘ve done it a few times, you can go through the settings and status pretty quickly. Analyzing MySQL

Post: Emulating global transaction ID with pt-heartbeat

of MySQL. A global transaction ID lets you determine a server‘s replication position reliably, among other benefits. This is great when youone for you if you want (or look in the documentation to see how to do it yourself), and start an instance of pt-heartbeat per server

Post: Identifying the load with the help of pt-query-digest and Percona Server

many tools out there that can make your life easy. However, there is oneyou can see there is a plethora of useful information reported by Percona Server. Another great thing about Percona Serverin memory. What it says though is that, if this query would run on a cold MySQL instance

Post: MySQL performance on EC2/EBS versus RDS

you need it to fit in memory. The largest instances currently have a bit less than 70GB of memory, so you canMySQL versus RDS, in most cases, unless you use Percona Server; but it’s still not orders-of-magnitude different. So my experience is that you can

Post: MySQL 5.5.8 and Percona Server: being adaptive

of neighborhood pages (not available in MySQL 5.5.8). The problem with flushing neighborhood pages is that it makes an exact calculation of how manyYou can see that MySQL 5.5.8 has periodic drops here, too. The margin between Percona Server and MySQL

Post: MySQL on Amazon RDS part 2: Determining Peak Throughput

server in the Joyent cloud. As a reminder, my goal was to run a long-term benchmark and see how the instance performed over time. Canof the benchmarks I ran. While running the benchmarks, I gathered many gigabytes of

Post: The story of one MySQL Upgrade

MySQL from one of very early MySQL 5.0 versions to Percona Server 5.1. This was a classical upgrade scenario which canof applications written by manyin this instance so it was done. So replication was running

Post: MySQL Replication vs DRBD Battles

of killing one of the nodes and re-syncing from another one while with MySQL Replication you can use Maatkit to merge the changes after all, also you canRunning two instances on the server allows to reduce hardware waste with DRBD, though not eliminate because you get some disks which you can

Post: Death match! EBS versus SSD price, performance, and QoS

many times, and cause trouble at other times. Inin a mirrored pair, is roughly 50% read utilized. This is one of the reasons I wrote the diskstats tool — you canrunning in the Amazon cloud. It’s a quadruple extra large EC2 server (currently priced at $2/hour for a non-reserved instance