Right now we’re launching I4g cases powered by AWS Graviton2 processors that ship as much as 15% higher compute efficiency than our different storage-optimized cases.
With as much as 64 vCPUs, 512 GiB of reminiscence, and 15 TB of NVMe storage, one of many six occasion sizes is certain to be an ideal match to your storage-intensive workloads: relational and non-relational databases, engines like google, file methods, in-memory analytics, batch processing, streaming, and so forth. These workloads are usually very delicate to I/O latency, and require loads of random learn/write IOPS together with excessive CPU efficiency.
Listed here are the specs:
Occasion Identify | vCPUs |
Reminiscence |
Storage |
Community Bandwidth |
EBS Bandwidth |
i4g.giant | 2 | 16 GiB | 468 GB | as much as 10 Gbps | as much as 40 Gbps |
i4g.xlarge | 4 | 32GiB | 937 GB | as much as 10 Gbps | as much as 40 Gbps |
i4g.2xlarge | 8 | 64 GiB | 1.875 TB | as much as 12 Gbps | as much as 40 Gbps |
i4g.4xlarge | 16 | 128 GiB | 3.750 TB | as much as 25 Gbps | as much as 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 cases make use of AWS Nitro SSDs (learn AWS Nitro SSD – Excessive Efficiency Storage to your I/O-Intensive Purposes to study extra) for NVMe storage. Every storage quantity can ship the next efficiency (all measured utilizing 4 KiB blocks):
- As much as 800K random write IOPS
- As much as 1 million random learn IOPS
- As much as 5600 MB/second of sequential writes
- As much as 8000 MB/second of sequential reads
Torn Write Safety is supported for 4 KiB, 8 KiB, and 16 KiB blocks.
Accessible Now
I4g cases can be found right this moment within the US East (Ohio, N. Virginia), US West (Oregon), and Europe (Eire) AWS Areas in On-Demand, Spot, Reserved Occasion, and Financial savings Plan type.
— Jeff;