Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Latest commit

 

History

History
96 lines (66 loc) · 11.1 KB

provisioned-iops.md

File metadata and controls

96 lines (66 loc) · 11.1 KB
Raw

Provisioned IOPS SSD volumes

Provisioned IOPS SSD volumes are backed by solid-state drives (SSDs). They are the highest performance Amazon EBS storage volumes designed for critical, IOPS-intensive, and throughput-intensive workloads that require low latency.

Amazon EBS offers three types of Provisioned IOPS SSD volumes:

  • Provisioned IOPS SSD (io2) volumes
  • Provisioned IOPS SSD (io2) Block Express volumes
  • Provisioned IOPS SSD (io1) volumes

Topics

Provisioned IOPS SSD (io1 and io2) volumes

Provisioned IOPS SSD (io1 and io2) volumes are designed to meet the needs of I/O-intensive workloads, particularly database workloads, that are sensitive to storage performance and consistency. Provisioned IOPS SSD volumes use a consistent IOPS rate, which you specify when you create the volume, and Amazon EBS delivers the provisioned performance 99.9 percent of the time.

io1 volumes are designed to provide 99.8 percent to 99.9 percent volume durability with an annual failure rate (AFR) no higher than 0.2 percent, which translates to a maximum of two volume failures per 1,000 running volumes over a one-year period. io2 volumes are designed to provide 99.999 percent volume durability with an AFR no higher than 0.001 percent, which translates to a single volume failure per 100,000 running volumes over a one-year period.

Provisioned IOPS SSD io1 and io2 volumes are available for all Amazon EC2 instance types. Provisioned IOPS SSD io2 volumes attached to C6a, C6in, C7g, Inf2, M6a, M6in, M6idn, M7g, R5b, R6in, R6idn, R7g, Trn1, Trn1n, X2idn, and X2iedn instances run on EBS Block Express. For more information, see io2 Block Express volumes.

Considerations for io2 volumes

  • io2 volumes are currently available in the following Regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Stockholm), and Middle East (Bahrain).
  • Keep the following in mind when launching instances with io2 volumes:
    • If you launch an instance with an io2 volume using an instance type that supports Block Express, the volume automatically runs on Block Express, regardless of the volume's size and IOPS.
    • You can't launch an instance type that does not support Block Express with an io2 volume that has a size greater than 16 TiB or IOPS greater than 64,000.
    • You can't launch an instance with an encrypted io2 volume that has a size greater than 16 TiB or IOPS greater than 64,000 from an unencrypted AMI or a shared encrypted AMI with Block Express. In this case, you must first create an encrypted AMI in your account and then use that AMI to launch the instance.
  • Keep the following in mind when creating io2 volumes:
    • If you create an io2 volume with a size greater than 16 TiB or IOPS greater than 64,000 in a Region where Block Express is supported, the volume automatically runs on Block Express.
    • You can't create an io2 volume with a size greater than 16 TiB or IOPS greater than 64,000 in a Region where Block Express is not supported.
    • If you create an io2 volume with a size of 16 TiB or less and IOPS of 64,000 or less in a Region where Block Express is supported, the volume does not run on Block Express.
    • You can't create an encrypted io2 volume that has a size greater than 16 TiB or IOPS greater than 64,000 from an unencrypted snapshot or a shared encrypted snapshot. In this case, you must first create an encrypted snapshot in your account and then use that snapshot to create the volume.
  • Keep the following in mind when attaching io2 volumes to instances:
    • If you attach an io2 volume to an instance that supports Block Express, the volume automatically runs on Block Express. It can take up to 48 hours to optimize the volume for Block Express. During this time, the volume provides io2 latency. After the volume has been optimized, it provides the sub-millisecond latency supported by Block Express.
    • You can't attach an io2 volume with a size greater than 16 TiB or IOPS greater than 64,000 to an instance type that does not support Block Express.
    • If you detach an io2 volume with a size of 16 TiB or less and IOPS of 64,000 or less from an instance that supports Block Express and attach it to an instance type that does not support Block Express, the volume no longer runs on Block Express and it provides io2 latency.
  • Keep the following in mind when modifying io2 volumes:
    • You can't modify an io2 volume and increase its size beyond 16 TiB or its IOPS beyond 64,000 while it is attached to an instance type that does not support Block Express.

Performance
Provisioned IOPS SSD volumes can range in size from 4 GiB to 16 TiB and you can provision from 100 IOPS up to 64,000 IOPS per volume. You can achieve up to 64,000 IOPS only on Instances built on the Nitro System. On other instance families you can achieve performance up to 32,000 IOPS. The maximum ratio of provisioned IOPS to requested volume size (in GiB) is 50:1 for io1 volumes, and 500:1 for io2 volumes. For example, a 100 GiB io1 volume can be provisioned with up to 5,000 IOPS, while a 100 GiB io2 volume can be provisioned with up to 50,000 IOPS. On a supported instance type, the following volume sizes allow provisioning up to the 64,000 IOPS maximum:

  • io1 volume 1,280 GiB in size or greater (50 × 1,280 GiB = 64,000 IOPS)
  • io2 volume 128 GiB in size or greater (500 × 128 GiB = 64,000 IOPS)

Provisioned IOPS SSD volumes provisioned with up to 32,000 IOPS support a maximum I/O size of 256 KiB and yield as much as 500 MiB/s of throughput. With the I/O size at the maximum, peak throughput is reached at 2,000 IOPS. Volumes provisioned with more than 32,000 IOPS (up to the maximum of 64,000 IOPS) yield a linear increase in throughput at a rate of 16 KiB per provisioned IOPS. For example, a volume provisioned with 48,000 IOPS can support up to 750 MiB/s of throughput (16 KiB per provisioned IOPS × 48,000 provisioned IOPS = 750 MiB/s). To achieve the maximum throughput of 1,000 MiB/s, a volume must be provisioned with 64,000 IOPS (16 KiB per provisioned IOPS × 64,000 provisioned IOPS = 1,000 MiB/s). The following graph illustrates these performance characteristics:

[Throughput limits for io1 volumes]

Your per-I/O latency experience depends on the provisioned IOPS and on your workload profile. For the best I/O latency experience, ensure that you provision IOPS to meet the I/O profile of your workload.

io2 Block Express volumes

Note
io2 Block Express volumes are supported with C6a, C6in, C7g, Inf2, M6a, M6in, M6idn, M7g, R5b, R6in, R6idn, R7g, Trn1, Trn1n, X2idn, and X2iedn instances.

io2 Block Express volumes is the next generation of Amazon EBS storage server architecture. It has been built for the purpose of meeting the performance requirements of the most demanding I/O intensive applications that run on Nitro-based Amazon EC2 instances.

Block Express architecture increases performance and scale. Block Express servers communicate with Nitro-based instances using the Scalable Reliable Datagram (SRD) networking protocol. This interface is implemented in the Nitro Card dedicated for Amazon EBS I/O function on the host hardware of the instance. It minimizes I/O delay and latency variation (network jitter), which provides faster and more consistent performance for your applications. For more information, see io2 Block Express volumes.

io2 Block Express volumes are suited for workloads that benefit from a single volume that provides sub-millisecond latency, and supports higher IOPS, higher throughput, and larger capacity than io2 volumes.

io2 Block Express volumes support the same features as io2 volumes, including Multi-Attach and encryption.

Note
You can't attach a Multi-Attach enabled io2 volume to instance types that support Block Express and instance types that do not support Block Express at the same time. For more information, see Attach a volume to multiple instances with Amazon EBS Multi-Attach.

Topics

Considerations

  • io2 Block Express volumes are currently supported with C6a, C6in, C7g, Inf2, M6a, M6in, M6idn, M7g, R5b, R6in, R6idn, R7g, Trn1, Trn1n, X2idn, and X2iedn instances.
  • io2 Block Express volumes are currently available in all Regions where supported instances are available, including US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), and Europe (Stockholm). Instance availability might vary by Availability Zone. For more information, see Find an Amazon EC2 instance type.

Performance

With io2 Block Express volumes, you can provision volumes with:

  • Sub-millisecond average latency
  • Storage capacity up to 64 TiB (65,536 GiB)
  • Provisioned IOPS up to 256,000, with an IOPS:GiB ratio of 1,000:1. Maximum IOPS can be provisioned with volumes 256 GiB in size and larger (1,000 IOPS × 256 GiB = 256,000 IOPS).
  • Volume throughput up to 4,000 MiB/s. Throughput scales proportionally up to 0.256 MiB/s per provisioned IOPS. Maximum throughput can be achieved at 16,000 IOPS or higher.

[Throughput limits for io2 Block Express volumes]

Quotas

io2 Block Express volumes adhere to the same service quotas as io2 volumes. For more information, see Amazon EBS quotas.

Pricing and billing

io2 volumes and io2 Block Express volumes are billed at the same rate. For more information, see Amazon EBS pricing.

Usage reports do not distinguish between io2 Block Express volumes and io2 volumes. We recommend that you use tags to help you identify costs associated with io2 Block Express volumes.