[ad_1]
|
Today we are launching I4g instances powered by AWS Graviton2 processors that deliver up to 15% better compute performance than our other storage-optimized instances.
With up to 64 vCPUs, 512 GiB of memory, and 15 TB of NVMe storage, one of the six instance sizes is bound to be a great fit for your storage-intensive workloads: relational and non-relational databases, search engines, file systems, in-memory analytics, batch processing, streaming, and so forth. These workloads are generally very sensitive to I/O latency, and require plenty of random read/write IOPS along with high CPU performance.
Here are the specs:
| Instance Name | vCPUs |
Memory |
Storage |
Network Bandwidth |
EBS Bandwidth |
| i4g.large | 2 | 16 GiB | 468 GB | up to 10 Gbps | up to 40 Gbps |
| i4g.xlarge | 4 | 32GiB | 937 GB | up to 10 Gbps | up to 40 Gbps |
| i4g.2xlarge | 8 | 64 GiB | 1.875 TB | up to 12 Gbps | up to 40 Gbps |
| i4g.4xlarge | 16 | 128 GiB | 3.750 TB | up to 25 Gbps | up to 40 Gbps |
| i4g.8xlarge | 32 | 256 GiB | 7.500 TB (2 x 3.750 TB) |
18.750 Gbps | 40 Gbps |
| i4g.16xlarge | 64 | 512 GiB | 15.000 TB (4 x 3.750 TB) |
37.500 Gbps | 80 Gbps |
The I4g instances make use of AWS Nitro SSDs (read AWS Nitro SSD – High Performance Storage for your I/O-Intensive Applications to learn more) for NVMe storage. Each storage volume can deliver the following performance (all measured using 4 KiB blocks):
- Up to 800K random write IOPS
- Up to 1 million random read IOPS
- Up to 5600 MB/second of sequential writes
- Up to 8000 MB/second of sequential reads
Torn Write Protection is supported for 4 KiB, 8 KiB, and 16 KiB blocks.
Available Now
I4g instances are available today in the US East (Ohio, N. Virginia), US West (Oregon), and Europe (Ireland) AWS Regions in On-Demand, Spot, Reserved Instance, and Savings Plan form.
— Jeff;
[ad_2]
Source link
