<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/atom10full.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0"><id>tag:blogger.com,1999:blog-3247171317808202855</id><updated>2008-06-25T05:08:26.875-07:00</updated><title type="text">DBA Dojo</title><link rel="alternate" type="text/html" href="http://blog.dbadojo.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default?start-index=26&amp;max-results=25&amp;redirect=false" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/posts/default" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>44</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/DbaDojo" type="application/atom+xml" /><feedburner:emailServiceId>1029533</feedburner:emailServiceId><feedburner:feedburnerHostname>http://www.feedburner.com</feedburner:feedburnerHostname><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-6385884815448021676</id><published>2008-05-26T04:13:00.000-07:00</published><updated>2008-05-26T04:29:24.561-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">How to use EC2 mountpoints</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/298328520/how-to-use-ec2-mountpoints.html" title="How to use EC2 mountpoints" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=6385884815448021676" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/6385884815448021676/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6385884815448021676" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6385884815448021676" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">It has been quiet around here.  My workload has been high and I have been spending my down time reading, rather than experimenting and hence publishing.

Frederic commented in a recent post about Sysbench fileio benchmark.
If you want to see whole set of posts use EC2 Benchmark

There were three questions and my reply was going to be long. So now it is a post.

Questions:

/dev/sda/ : do you mean&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=Qxh5MH"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=Qxh5MH" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/05/how-to-use-ec2-mountpoints.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-8918323391151446461</id><published>2008-04-16T04:00:00.000-07:00</published><updated>2008-04-16T04:42:50.009-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Sysbench fileio vs XLarge EC2 Part 3</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/271374187/sysbench-fileio-vs-xlarge-ec2-part-3.html" title="Sysbench fileio vs XLarge EC2 Part 3" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=8918323391151446461" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/8918323391151446461/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8918323391151446461" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8918323391151446461" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Background:

If you have been following the series. I have gone back to checking the raw IO performance of all the Amazon EC2 instances.
Sysbench fileio vs EC2 Part 1
Sysbench fileio vs Large EC2 Part 2
seeker io benchmark vs EC2

In the meantime Amazon has finally announced that they are providing persistent storage for all EC2 instances. This has removed a bunch of complexity from running a &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=wiTJzOG"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=wiTJzOG" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/04/sysbench-fileio-vs-xlarge-ec2-part-3.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-7681496994475067209</id><published>2008-04-05T18:28:00.001-07:00</published><updated>2008-04-06T05:06:07.446-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Oracle" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Is EC2 useful as a database server</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/264830714/is-ec2-useful-as-database-server.html" title="Is EC2 useful as a database server" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=7681496994475067209" title="4 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/7681496994475067209/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/7681496994475067209" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/7681496994475067209" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Plenty of people have been excited by the prospect of Amazon EC2 and the ability to scale out your databases as load increases from your original configuration. I noticed Morgan Tocker and Carl Mercier are going to be presenting on this topic at the upcoming MySQL Conference

However almost immediately people are worried about the lack of persistent of data across instance terminations.
In a &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=qfXoRpG"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=qfXoRpG" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/04/is-ec2-useful-as-database-server.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-6714986396587413597</id><published>2008-03-25T06:35:00.000-07:00</published><updated>2008-03-25T03:36:55.579-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Sysbench fileio vs Large EC2 Part 2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/257579698/sysbench-fileio-vs-large-ec2-part-2.html" title="Sysbench fileio vs Large EC2 Part 2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=6714986396587413597" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/6714986396587413597/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6714986396587413597" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6714986396587413597" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Overview:

I reran the sysbench fileio benchmarking tool on a large EC2 instance. This is basically the middle range offering from Amazon. The large instance runs a 64 bit OS of your choice and safely sits in the commodity PC/Server range (with a little extra memory).

If you missed the first article, I ran the same sysbench fileio benchmark on the small EC2 instance

Install:
Follow the &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=ocVpzIF"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=ocVpzIF" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/03/sysbench-fileio-vs-large-ec2-part-2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-2741765837865860062</id><published>2008-03-25T03:39:00.000-07:00</published><updated>2008-03-25T04:26:45.721-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Seeker io benchmark on small EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/257603498/seeker-io-benchmark-on-small-ec2.html" title="Seeker io benchmark on small EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=2741765837865860062" title="1 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/2741765837865860062/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2741765837865860062" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2741765837865860062" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Frederic posted an interesting link to the seeker io script in the sysbench fileio vs small EC2 article.

He was concerned that the seeker was showing difference numbers to sysbench fileio, especially on the /mnt mountpoint.

I read the thread and there was another comment made concerning how Xen could use a sparse file image to improve the io performance. I tested that theory out and found as &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=CgvKAeF"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=CgvKAeF" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/03/seeker-io-benchmark-on-small-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5788531857546852</id><published>2008-03-12T03:22:00.000-07:00</published><updated>2008-03-12T05:03:14.842-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Sysbench fileio vs EC2 Part 1</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/250070084/sysbench-fileio-vs-ec2-part-1.html" title="Sysbench fileio vs EC2 Part 1" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5788531857546852" title="5 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5788531857546852/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5788531857546852" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5788531857546852" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Overview:

Peter Zaitsev's recent article about Evaluating IO subsystem performance for MySQL spurred my interest in doing something similar on EC2.

I have covered running sysbench against MySQL on EC2 however not specifically used sysbench to test IO. Rather I had used bonnie++ and iozone to do that.

I don't have a lot of respect for the EC2 small instance. Whilst it was reasonable in the &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=OipXIdF"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=OipXIdF" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/03/sysbench-fileio-vs-ec2-part-1.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5028436415482708501</id><published>2008-03-04T02:19:00.000-08:00</published><updated>2008-03-04T02:47:40.096-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Maatkit" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL Master-Master replication table sync</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/245424601/mysql-master-master-replication-table.html" title="MySQL Master-Master replication table sync" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5028436415482708501" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5028436415482708501/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5028436415482708501" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5028436415482708501" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">I saw a post by Baron mentioning that his tool maatkit is best for handling situations where a master-master replication setup has got out of sync.

If you think Baron was blowing his own trumpet he has good reason to. I have used his mk-archiver tool as part of the Maatkit to make the problem of archiving and purging data much easier. This was much easier than rolling my own solution.

Anyhow. I&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=H81UJqF"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=H81UJqF" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/03/mysql-master-master-replication-table.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-182545550074141268</id><published>2008-02-26T03:41:00.000-08:00</published><updated>2008-02-26T04:32:08.356-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Replication" /><category scheme="http://www.blogger.com/atom/ns#" term="MIMM" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL Multi Master-Master on EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/241465916/mysql-multi-master-master-on-ec2.html" title="MySQL Multi Master-Master on EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=182545550074141268" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/182545550074141268/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/182545550074141268" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/182545550074141268" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Background:

As I mentioned in the previous post on running multiple mysql instances on EC2 using mysqld_multi. This was the first step in running 2 or more EC2 Amazon Machine Image (AMI) as a Multi-instance Master-Master (MIMM)  replication cluster.
The idea cames from a blog article from Apokalyptik.com
It is about improving the availability of your databases on EC2 and allowing easy backups &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=x7ZAAWE"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=x7ZAAWE" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/02/mysql-multi-master-master-on-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-389649190397614719</id><published>2008-02-13T01:56:00.001-08:00</published><updated>2008-02-13T02:29:05.391-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="SolidDB" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL SolidDB vs MySQLSlap EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/234285662/mysql-soliddb-vs-mysqlslap-ec2.html" title="MySQL SolidDB vs MySQLSlap EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=389649190397614719" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/389649190397614719/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/389649190397614719" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/389649190397614719" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Overview:

I am always keen to try and test out new technologies. The idea of having a choice in storage engines is a great feature of MySQL. In MySQL 5.1, the MySQL engine API is available to write your own storage engine.

In the meantime, there are a couple of MySQL storage engines produced by 3rd party companies. SolidDB is one of them.

I wanted to install and then test the SolidDB engine &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=EujxOLE"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=EujxOLE" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/02/mysql-soliddb-vs-mysqlslap-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-2814667754811567951</id><published>2008-02-02T16:03:00.000-08:00</published><updated>2008-02-03T22:46:03.526-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="mysqlslap" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL vs MySQLSlap Round 3</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/228740574/mysql-vs-mysqlslap-round-3.html" title="MySQL vs MySQLSlap Round 3" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=2814667754811567951" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/2814667754811567951/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2814667754811567951" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2814667754811567951" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">In this continuing series on using mysqlslap to pound mysql databases.
http://blog.dbadojo.com/2007/08/mysql-vs-mysqlslap.html
http://blog.dbadojo.com/2008/01/mysql-vs-mysqlslap-round-2.html

I was moving towards running mysqlslap to test any concurrency limits inherent in mysql-proxy. However I was unable to get the small instances on EC2 to handle even small concurrent levels (500 concurrent &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=vmXl1KE"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=vmXl1KE" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/02/mysql-vs-mysqlslap-round-3.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-1924176992761856880</id><published>2008-01-23T02:07:00.000-08:00</published><updated>2008-03-24T02:44:19.088-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="mysqlslap" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL vs MySQLslap round 2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/221570389/mysql-vs-mysqlslap-round-2.html" title="MySQL vs MySQLslap round 2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=1924176992761856880" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/1924176992761856880/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/1924176992761856880" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/1924176992761856880" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">I was going to post some more on the clash of the titans i.e. mysql-proxy vs mysqlslap, however after doing some retesting, I never got past ramping the number of concurrent sessions in mysqlslap.

I wanted to make sure the Mysql database could handle the raw load, before adding another layer in the form of mysql-proxy.

Back in August I did some preliminary work with MySQL and mysqlslap.

So &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=EuJozmD"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=EuJozmD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/01/mysql-vs-mysqlslap-round-2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-8914903709066152319</id><published>2008-01-14T03:22:00.000-08:00</published><updated>2008-01-14T03:42:41.503-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="MySQL proxy" /><title type="text">MySQL-Proxy vs MySQLSlap Round 1</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/216388086/mysql-proxy-vs-mysqlslap-round-1.html" title="MySQL-Proxy vs MySQLSlap Round 1" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=8914903709066152319" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/8914903709066152319/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8914903709066152319" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8914903709066152319" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Outline:

Given the mysql-proxy is moving toward a production ready version (at some point). I thought it would be useful to put it up against mysqlslap and see how it fared.

In this round, I wanted to see if mysql-proxy could handle various workloads and concurrent connections in the plain vanilla load-balancing state.

Essentially we are building on past experience.
http://blog.dbadojo.com/&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=6rXHdbD"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=6rXHdbD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/01/mysql-proxy-vs-mysqlslap-round-1.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5784540557032673113</id><published>2008-01-03T03:57:00.000-08:00</published><updated>2008-01-03T22:08:24.844-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Multiple MySQL instances on EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/210477923/multiple-mysql-instances-on-ec2.html" title="Multiple MySQL instances on EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5784540557032673113" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5784540557032673113/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5784540557032673113" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5784540557032673113" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Overview:

I am keen to see what other people's thoughts of MySQL and using MySQL on EC2 are in general. So I read any blogs which discuss them with interest.

In the latter part of last year I read an interesting article on proposing to run multiple MySQL instances on a single EC2.

Running multiple MySQL instances on one box is reasonably straightforward. Most of the exposure I have seen is &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=P3QXtWD"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=P3QXtWD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2008/01/multiple-mysql-instances-on-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5143179446941028408</id><published>2007-12-08T20:54:00.000-08:00</published><updated>2008-01-03T22:08:11.466-08:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="MySQL proxy" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL Proxy on EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/197435624/mysql-proxy-on-ec2.html" title="MySQL Proxy on EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5143179446941028408" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5143179446941028408/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5143179446941028408" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5143179446941028408" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">MySQL Proxy is a tool to sit between the client and database. It can load balance, redirect queries, track slow queries amongst other possible uses.

http://dev.mysql.com/doc/refman/5.0/en/mysql-proxy.html
http://forge.mysql.com/wiki/MySQL_Proxy


There is a ramp up within MySQL to get MySQL Proxy into a production ready product. So it is time to check out the product and see if the stated simple&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=xf7od0C"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=xf7od0C" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/12/mysql-proxy-on-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5225827458149500862</id><published>2007-11-30T20:49:00.000-08:00</published><updated>2008-03-24T02:44:19.089-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="LVM" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Making Logical Volumes on EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/193319149/making-logical-volumes-on-ec2.html" title="Making Logical Volumes on EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5225827458149500862" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5225827458149500862/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5225827458149500862" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5225827458149500862" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">The MySQL backups using LVM Snapshots post is now by far the most popular post.


Here is shell script which helps get the Logical Volumes (LV) setup in the first place.


### START OF SCRIPT ###

#!/bin/sh
# Name: make_mnt_LV.sh
# Script to make EC2 /mnt into a LVM volume

modprobe dm-snapshot

umount /mnt
pvcreate /dev/sda2
vgcreate vg /dev/sda2
lvcreate -L30720M -n myvmdisk1 vg
mkfs -t ext3 /&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=t5MAGEB"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=t5MAGEB" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/11/making-logical-volumes-on-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-6063762590924038440</id><published>2007-11-19T01:27:00.000-08:00</published><updated>2008-03-12T04:23:52.510-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Sysbench vs MySQL on EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/187083500/sysbench-vs-mysql-on-ec2.html" title="Sysbench vs MySQL on EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=6063762590924038440" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/6063762590924038440/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6063762590924038440" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6063762590924038440" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">I was reading how Morgan was slightly disappointed at the results of his sysbench test. He ran sysbench on his laptop and then on EC2 and got a large difference in the results. Thorsten from RightScale also ran some sysbench tests.

I was keen to either replicate or disprove their results. Given their parameters I replicated their results.
Rather than stop there, I decided to see what was main &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=zVERFLB"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=zVERFLB" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/11/sysbench-vs-mysql-on-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-2360691796485091408</id><published>2007-10-29T04:56:00.000-07:00</published><updated>2008-03-12T04:23:30.856-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">IOZone benchmark vs EC2 heat maps</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/176646494/iozone-benchmark-vs-ec2-heat-maps.html" title="IOZone benchmark vs EC2 heat maps" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=2360691796485091408" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/2360691796485091408/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2360691796485091408" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2360691796485091408" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">



I have been using the IOZone benchmarking tool to test the IO ability of EC2 running CentOS 4.

In the last post I showed the 3D surface area chart showing how as the file size grows, the io performance degrades, quite sharply as the file migrates from CPU cache to memory cache to disk.

I redid the charts as what Excel calls contour charts, but remind me of heat maps.

The change was &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=FAJpsBA"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=FAJpsBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/10/iozone-benchmark-vs-ec2-heat-maps.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-8924158391861578027</id><published>2007-10-18T04:54:00.000-07:00</published><updated>2008-03-12T04:23:30.857-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">IOzone benchmark vs EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/171580112/iozone-benchmark-vs-ec2.html" title="IOzone benchmark vs EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=8924158391861578027" title="2 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/8924158391861578027/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8924158391861578027" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8924158391861578027" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">



Here are some pretty surface area graphs from the EC2 benchmark, the stepping down indicates from CPU cache to Memory cache, the last cliff is down to disk once the file was larger the available memory.

As I mentioned yesterday I was running off a IOzone benchmark on EC2 to see how the disk performs, after reading about it in this online benchmark article.
There are a couple of nice features&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=yUOAeVA"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=yUOAeVA" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/10/iozone-benchmark-vs-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-2476304771680339294</id><published>2007-10-17T05:22:00.000-07:00</published><updated>2007-10-17T05:34:58.569-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="popular" /><title type="text">Top 9 Most popular articles so far</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/171110499/top-9-most-popular-articles-so-far.html" title="Top 9 Most popular articles so far" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=2476304771680339294" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/2476304771680339294/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2476304771680339294" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/2476304771680339294" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Whilst I have a iozone benchmark running in the background, I thought I would post a quick article listing the top 9 pages on the site up to now (October 2007).

As most people don't always hit the front page and more than 85%-90% of all visitors are new I thought it would be useful for those people to see what else is floating around on the site.

Installing Oracle 11G using a silent install &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=1vzoIrVy"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=1vzoIrVy" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/10/top-9-most-popular-articles-so-far.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-929064568955106393</id><published>2007-10-04T04:45:00.000-07:00</published><updated>2008-03-12T04:23:30.858-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">Bonnie IO Benchmark vs EC2</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/165186886/bonnie-io-benchmark-vs-ec2.html" title="Bonnie IO Benchmark vs EC2" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=929064568955106393" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/929064568955106393/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/929064568955106393" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/929064568955106393" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Andy, a reader of the blog left a comment asking if I could run some benchmarking of EC2.

If someone takes the time to comment, making the effort to respond is always worthwhile. Feedback drives most conversation, business and innovation.

So I went off and google'ed the most appropriate and easiest benchmarking tool.

http://www.tux.org/pub/benchmarks/
http://oss.sgi.com/LDP/HOWTO/&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=GaQK8rGU"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=GaQK8rGU" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/10/bonnie-io-benchmark-vs-ec2.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-6283722690918816604</id><published>2007-09-21T19:38:00.000-07:00</published><updated>2007-09-21T20:19:53.776-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="mysqltoolkit" /><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><title type="text">MySQLtoolkit: mysql-table-checksum</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/159738704/mysqltoolkit-mysql-table-checksum.html" title="MySQLtoolkit: mysql-table-checksum" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=6283722690918816604" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/6283722690918816604/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6283722690918816604" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/6283722690918816604" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Mysqltoolkit is a bunch of MySQL utilities based on perl written by Baron Schwartz.

Essentially he found no tool or software available to help him, so decided to write his own.
Not only that, he turned around and released them for any DBA to use.

As soon as I reviewed the list of tools available I immediately wanted to give mysql-table-checksum a test. Like many DBAs who support MySQL, &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=5Rdr7IDp"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=5Rdr7IDp" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/09/mysqltoolkit-mysql-table-checksum.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-9201118265809961214</id><published>2007-09-16T01:17:00.000-07:00</published><updated>2007-09-16T01:34:30.242-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="roadmap" /><title type="text">Future Posting Roadmap: 2007</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/157124756/future-posting-roadmap-2007.html" title="Future Posting Roadmap: 2007" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=9201118265809961214" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/9201118265809961214/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/9201118265809961214" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/9201118265809961214" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">Posting has been lighter than normal, as I have had the flu and it is footy finals time in Australia.

However I sat down the other day and thought about which areas I hope to cover over the next couple of months.
Given this is a blog and comments are on, if you want something covered which is not on the list feel free to add a comment with a request.

Topics:

Replication:

Determine the IO/sec &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=1iSSS9nW"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=1iSSS9nW" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/09/future-posting-roadmap-2007.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-4394919919215687434</id><published>2007-09-08T04:24:00.000-07:00</published><updated>2008-03-12T04:26:21.843-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL Backups using LVM snapshots</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/153831094/mysql-backups-using-lvm-snapshots.html" title="MySQL Backups using LVM snapshots" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=4394919919215687434" title="7 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/4394919919215687434/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/4394919919215687434" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/4394919919215687434" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">There are a couple of options available to get consistent backups from MySQL.
Use mysqldump with FLUSH TABLES WITH READ LOCKUse a slave with STOP SLAVE and your favourite backup tool.
For innodb, use the commerical backup tool ibbackupUse LVM (Logical Volume Manager) snapshots with FLUSH TABLES WITH READ LOCKShutdown the database.We are going to demostrate how to use LVM snapshots to reduce time &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=BjNlykqD"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=BjNlykqD" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/09/mysql-backups-using-lvm-snapshots.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-5964412178080562754</id><published>2007-09-05T05:38:00.000-07:00</published><updated>2008-03-24T02:44:19.091-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">mysqlslap proves Innodb auto increment limits scalability</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/152494162/mysqlslap-proves-innodb-auto-increment.html" title="mysqlslap proves Innodb auto increment limits scalability" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=5964412178080562754" title="0 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/5964412178080562754/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5964412178080562754" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/5964412178080562754" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">
I was testing some mysqlslap runs which Brian 'Krow' Aker was running testing the effect of changing the commit interval. Whilst I was doing that I noticed that he had added the option to add an auto incrementing column to the generated table.

Having read elsewhere here and here that the way innodb handles auto incrementing columns can cause issues, I thought I would test that out. And as the &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=8Wmn3qgc"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=8Wmn3qgc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/09/mysqlslap-proves-innodb-auto-increment.html</feedburner:origLink></entry><entry><id>tag:blogger.com,1999:blog-3247171317808202855.post-8086297554796970401</id><published>2007-08-31T19:16:00.001-07:00</published><updated>2008-03-12T04:23:30.860-07:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="MySQL" /><category scheme="http://www.blogger.com/atom/ns#" term="Benchmark" /><category scheme="http://www.blogger.com/atom/ns#" term="EC2" /><title type="text">MySQL DBT2 Benchmark on EC2 part 1</title><link rel="alternate" type="text/html" href="http://feeds.feedburner.com/~r/DbaDojo/~3/150800098/mysql-dbt2-benchmark-on-ec2-part-1_31.html" title="MySQL DBT2 Benchmark on EC2 part 1" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=3247171317808202855&amp;postID=8086297554796970401" title="5 Comments" /><link rel="replies" type="application/atom+xml" href="http://blog.dbadojo.com/feeds/8086297554796970401/comments/default" title="Post Comments" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8086297554796970401" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/3247171317808202855/posts/default/8086297554796970401" /><author><name>roobaron</name><uri>http://www.blogger.com/profile/08420801903669108937</uri><email>noreply@blogger.com</email></author><content type="html">In the last couple of articles I have been using the load simulator/generator tool provided with the MySQL 5.1 install called mysqlslap.

I read around on some other blogs and thought it might be also useful to use a benchmarking tool. DBT2 is a TPC-C like benchmark tool provided by OSDL. You can download the software from the DBT sourceforge site.

The TPC-C is a online transaction test &lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/DbaDojo?a=OWwBAACo"&gt;&lt;img src="http://feeds.feedburner.com/~f/DbaDojo?i=OWwBAACo" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</content><feedburner:origLink>http://blog.dbadojo.com/2007/08/mysql-dbt2-benchmark-on-ec2-part-1_31.html</feedburner:origLink></entry></feed>
