Now available: Amazon EC2 M9g and M9gd instances powered by new AWS Graviton5 processors
AWS has released new EC2 instance types—M9g and M9gd—built on the latest AWS Graviton5 processor. If you’ve been following the evolution of AWS-custom silicon, this is a meaningful step forward. Graviton5 delivers up to 25% better compute performance than its Graviton4 predecessor while maintaining AWS’s focus on energy efficiency. For teams running containerized workloads, microservices, or general-purpose applications, this means more capability per dollar and per watt consumed.
The technical improvement comes from a redesigned processor architecture. Graviton5 increases clock speeds, improves instruction throughput, and enhances memory bandwidth compared to Graviton4. The M-series instances are general-purpose machines—they balance compute, memory, and network resources—making them suitable for a wide range of workloads. The key distinction: M9g instances come with local NVMe SSD storage (the “d” in M9gd), which helps if your application needs fast, temporary storage without making extra API calls to EBS. For Python-based batch jobs, Node.js APIs, or containerized applications using Docker and Kubernetes, these instances fit naturally into existing architectures.
Why this matters comes down to economics and sustainability. A 25% performance improvement means you can either handle more throughput on the same instance size or downsize your instance type and maintain current performance—directly reducing your monthly AWS bill. Because Graviton5 is more energy efficient, your cost savings compound with lower data center power consumption. If you’re running auto-scaling groups with dozens or hundreds of instances, or if you operate applications 24/7, those percentage improvements add up quickly.
Consider a concrete scenario: a team running Node.js microservices in ECS on M7g instances today could migrate to M9g and see improved request handling without changing code. Or if you’re building a data processing pipeline in Python that’s CPU-bound—maybe analyzing logs or transforming datasets—the extra compute headroom might let you consolidate jobs that previously needed larger instances. The M9gd variant specifically helps if your application caches frequently-accessed data locally. As always with new instance types, the practical next step is testing in your own environment: spin up a test instance, run your actual workloads, and measure the difference before committing to a migration.