Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« The AWS Report - Dave Peck, Co-Founder of Cloak | Main | AWS Week in Review - July 30, 2012 »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef016306920b34970d

Listed below are links to weblogs that reference Fast Forward - Provisioned IOPS for EBS Volumes:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Adriaan

Really awesome, the innovation never seems to stop with AWS.
What is the typical IOPS rate of standard EBS Volumes? Can't wait to try it out on our EC2 Windows SQL DB's.

Frank

Amazing how close AWS is to what customers demand!
We had extensive discussions about EBS performance during my OZ workshop series.

Also I am looking forward to run some I/O benchmarks ;)

jpetazzo

@Adriaan: according to recent exchanges I had with AWS support, you should expect about 100 IOPS on a regular EBS volume.

Fred

Exciting feature!

How does this interact with reserved instances? If I have an existing m1.large reserved instance and I replace it with a m1.large, optimized for ebs instance does my previously purchased reservation carry over?

I believe RDS uses EBS for storage - will it be possible to configure RDS instances as optimized for EBS / turn on provisioned IOs for these ?

Jason Watts

The article mentions the standard rate is 100.

Adriaan

@jpetazzo thanks! so one can expect about x10 better read/write speed, and even faster later, really awesome.

Reynald

That's great!

One thing I couldn't find out how to do. Through the APIs, how can I know if a volume if IOPS provisioned and the number of IOPS ?

The info is not provided on describe-volume-attribute and on describe-volume.

thanks.

Chris

I second what Fred asked - how does this work with existing reserved instances? If I have an m1.xlarge reserved instance, is there a way to upgrade the reservation to include the EBS-optimized part?

dreik

and what's about ec2-modify-instance-attribute for m2.2xlarge?

Andrew Chilton

Have added support for EbsOptimized parameters to both StartInstances and ModifyInstanceAttributes to AwsSum. Other operations which have anything new at a lower level (ie. a complex data structure) don't need anything extra in my code, but I'm not entirely certain I have everything covered.

Is there any kind of ChangeLog page or API Announcement mailing list to find out when, but more importantly how, the API changes?

Many thanks,
Andy

Bradley

@Reynald, you can get this information from the latest version of the EC2 api tools, by calling ec2-describe-volumes

Eric Hammond

I've published some specific instructions on how to use the EC2 API command line tools to upgrade a running EC2 instance to an EBS-Optimized instance with Provisioned IOPS EBS volumes:

http://alestic.com/2012/08/ec2-provisioned-iops-ebs

While testing this I discovered some interesting limitations on the minimum size of the EBS volume (at least 10 GB and at least 1/10th in GB of the requested IOPS value).

fortran01

Can we not EBS optimize m2.2xlarge?

Marc Brooks

If I STOP, flip the flag and START, will I get a different internal/external IP?

Adriaan

Just converted our EBS volumes hosting large MS SQL Databases to IOPS 1000 ... awesome results so far!

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30