This is a continuation of my series of benchmark posts comparing Amazon RDS to a server running on Amazon EC2. Upcoming posts (probably 6 or 8 in total) will extend the scope of the benchmark to include data on our Dell r900 with traditional hard drives in RAID10, and a server in the Joyent cloud. [...]
MySQL on Amazon RDS part 1: insert performance
March 15, 2011 By 37 Comments
Amazon’s Relational Database Service (RDS) is a cloud-hosted MySQL solution. I’ve had some clients hitting performance limitations on standard EC2 servers with EBS volumes (see SSD versus EBS death match), and one of them wanted to evaluate RDS as a replacement. It is built on the same technologies, but the hardware and networking are supposed [...]
High availability for MySQL on Amazon EC2 – Part 6 – Publishing server location
February 16, 2011 By Leave a Comment
This post is the sixth of a series that started here. From the previous posts of this series, we now have an HA MySQL service running on EC2. We now need to find a way to point the web servers or application servers to the HA MySQL service. Normally, in an HA setup, this is [...]
High availability for MySQL on Amazon EC2 – Part 5 – The instance monitoring script
February 15, 2011 By 3 Comments
This post is the fifth of a series that started here. From the previous posts of this series, we now have nearly everything setup, only a few pieces are missing. One of the missing pieces is the Pacemaker script that run on the MySQL instance.
Sharing an auto_increment value across multiple MySQL tables (revisited)
October 26, 2010 By 7 Comments
A couple of weeks ago I blogged about Sharing an auto_increment value across multiple MySQL tables. In the comments, a few people wrote in to suggest alternative ways of implementing this. I just got around to benchmarking those alternatives today across two large EC2 machines:
High availability for MySQL on Amazon EC2 – Part 5 – The instance monitoring script
October 22, 2010 By Leave a Comment
This post is the fifth of a series that started here. From the previous posts of this series, we now have an instance restart script that can restart the database node in case of failure and automatically reconfigure Pacemaker and the other servers that needs to access the MySQL server. What we will cover in [...]
Percona Server with XtraDB Case Study, Behind the Scenes
October 21, 2010 By 13 Comments
We’ve published our first case study. The customer, ideeli, had a database that was struggling on standard MySQL and InnoDB. The big win was the upgrade to XtraDB. The business continued to grow quickly, and months later under much more traffic, the database is still outperforming their previous version. I thought I’d write a few [...]
Sharing an auto_increment value across multiple MySQL tables
October 4, 2010 By 9 Comments
The title is SEO bait – you can’t do it. We’ve seen a few recurring patterns trying to achieve similar – and I thought I would share with you my favorite two: Option #1: Use a table to insert into, and grab the insert_id:
1 2 3 4 5 | CREATE TABLE option1 (id int not null primary key auto_increment) engine=innodb; # each insert does one operations to get the value: INSERT INTO option1 VALUES (NULL); # $connection->insert_id(); |
Option #2: Use a table with one just row:
1 2 3 4 5 6 | CREATE TABLE option2 (id int not null primary key) engine=innodb; INSERT INTO option2 VALUES (1); # start from 1 # each insert does two operations to get the value: UPDATE option2 SET id=@id:=id+1; SELECT @id; |
High availability for MySQL on Amazon EC2 – Part 4 – The instance restart script
August 19, 2010 By 6 Comments
This post is the fourth of a series that started here. From the previous of this series, we now have resources configured but instead of starting MySQL, Pacemaker invokes a script to start (or restart) the EC2 instance running MySQL. This blog post describes the instance restart script. Remember, I am more a DBA than [...]
Announcing Training for Operations Teams
August 18, 2010 By 3 Comments
We’re opening up registration for our new training courses today. In short: we are moving from two days to a new four-day format. The new additions are created by: Splitting our current InnoDB day in half. We now have one day for DBAs, and one day just on InnoDB topics. A new Operations Day – covering [...]
