Not all database workloads are created equal. Some high-priority jobs require faster storage input/output operations per second than others. Now Amazon(s amzn) is acknowledging that fact with new provisioned IOPs for its Relational Database Service.
IOPs are basically the round trips data takes between database and storage. Amazon started offering analogous provisioned IOPS for its Elastic Block Storage (EBS), but is now expanding that capability to all of its supported databases, according to the Amazon Web Services blog. According to the blog:
Effective immediately, you can provision new RDS database instances with 1,000 to 10,000 IOPS, and with 100GB to 1 TB of storage for MySQL and Oracle databases. If you are using SQL Server, the maximum IOPS you can provision is 7,000 IOPS. All other RDS features including Multi-AZ, Read Replicas, and the Virtual Private Cloud, are also supported.
Note: developers will have to provision their maximum IOPS when they start out — and can scale up to that maximum over time. If they want to exceed their maximum they will have to start again.
Later on, users will be able to move existing legacy RDS instances to provisioned IOPS storage — at least for MySQL and Oracle(s orcl)databases. If those who just can’t wait, they can take existing data, export it and re-import it into a new database instance, according Amazon.
Amazon is known for releasing streams of new and enhanced features over time. That pace will likely continue or even hasten as more cloud competitors — Rackspace(s rax), HP(s hpq), et al — come online. Disk IO can be an issue for Amazon EC2 customers. One account told me this week that they’d moved some of their high I/O tasks from Amazon to Rackspace for this very reason.
For more, check out the video.