Comments on: Dissection of EC2 / EBS volume http://www.mysqlperformanceblog.com/2009/08/07/dissection-of-ec2-ebs-volume/ Percona's MySQL & InnoDB performance and scalability blog Sat, 11 Feb 2012 16:45:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Vadim http://www.mysqlperformanceblog.com/2009/08/07/dissection-of-ec2-ebs-volume/comment-page-1/#comment-635710 Vadim Sat, 22 Aug 2009 04:31:08 +0000 http://www.mysqlperformanceblog.com/?p=960#comment-635710 Ijonas, fixed, thanks! Ijonas,

fixed, thanks!

]]> By: Ijonas Kisselbach http://www.mysqlperformanceblog.com/2009/08/07/dissection-of-ec2-ebs-volume/comment-page-1/#comment-630986 Ijonas Kisselbach Sun, 16 Aug 2009 07:41:31 +0000 http://www.mysqlperformanceblog.com/?p=960#comment-630986 Your link to your previous post on "EC2/EBS single and RAID volumes IO benchmark" doesn't seem to work. Your link to your previous post on “EC2/EBS single and RAID volumes IO benchmark” doesn’t seem to work.

]]> By: peter http://www.mysqlperformanceblog.com/2009/08/07/dissection-of-ec2-ebs-volume/comment-page-1/#comment-627707 peter Tue, 11 Aug 2009 00:43:36 +0000 http://www.mysqlperformanceblog.com/?p=960#comment-627707 Vadim, Indeed. I also have seen cache on EC2 EBS. I do not think however it is something like 4 disk RAID you mention - it is all shared infrastructure to start with. I'd expect there is some cache which have certain performance - note the response time you're seeing are well below 5ms you would see from physical spinning drive. This is indeed challenge for "cloud" envinronment which is both shared as well as loosely specified - because you do not know how much cache you're dealing with you do not know if workload you're running is "cached" or not, this means you can't predict how performance will drop with data growth. Vadim,

Indeed. I also have seen cache on EC2 EBS. I do not think however it is something like 4 disk RAID you mention – it is all shared infrastructure to start with. I’d expect there is some cache which have certain performance – note the response time you’re seeing are well below 5ms you would see from physical spinning drive.

This is indeed challenge for “cloud” envinronment which is both shared as well as loosely specified – because you do not know how much cache you’re dealing with you do not know if workload you’re running is “cached” or not, this means you can’t predict how performance will drop with data growth.

]]> By: wizardofcrowds http://www.mysqlperformanceblog.com/2009/08/07/dissection-of-ec2-ebs-volume/comment-page-1/#comment-626124 wizardofcrowds Sat, 08 Aug 2009 04:33:32 +0000 http://www.mysqlperformanceblog.com/?p=960#comment-626124 This is somewhat very similar to what I found but much more primitive way. Here is a thread on EC2 developer forum. http://developer.amazonwebservices.com/connect/thread.jspa?messageID=110072 AndrewC@AWS said "There is no throttling per se on EBS; however, some of the system components are shared resources. You may experience contention, which can reduce your performance from the theoretical maximum. In this particular case, your first set of writes are serviced by writing into a cache. Eventually, the cache is full and then you are bound by the throughput of the underlying disk arrays." This is somewhat very similar to what I found but much more primitive way. Here is a thread on EC2 developer forum.

http://developer.amazonwebservices.com/connect/thread.jspa?messageID=110072

AndrewC@AWS said “There is no throttling per se on EBS; however, some of the system components are shared resources. You may experience contention, which can reduce your performance from the theoretical maximum. In this particular case, your first set of writes are serviced by writing into a cache. Eventually, the cache is full and then you are bound by the throughput of the underlying disk arrays.”

]]>