Every new Graviton generation creates the same opportunity: revisit workloads that were left on x86 because the migration did not feel urgent.
AWS announced Amazon EC2 C9g and C9gd instances powered by AWS Graviton5. The source article highlights higher performance per vCPU, faster memory, larger cache, stronger packet processing, higher network bandwidth, higher EBS bandwidth, and local NVMe on C9gd.
For builders, this is not just a new instance family. It is another chance to reduce compute cost without changing the application architecture.
What changed
C9g is compute-optimized Arm-based EC2 capacity. C9gd adds local NVMe SSD storage for workloads that need fast scratch space or low-latency local buffers.
The obvious candidates include:
- batch processing,
- CPU-based inference,
- real-time analytics,
- video encoding,
- distributed services,
- high-throughput application servers,
- compute-heavy CI workers,
- agentic workloads with many concurrent CPU-bound steps.
The article also calls out detailed NVMe statistics for Graviton5-based instance store volumes, which helps teams operate latency-sensitive local storage more carefully.
Why builders should care
Graviton migrations are often one of the cleaner cost-optimization paths because the architecture stays familiar. You are not introducing a new service. You are changing the processor architecture and validating the software stack.
For many managed runtimes, containers, and compiled languages, the compatibility story has improved significantly over the last few years. The remaining work is usually dependency validation, image build changes, performance testing, and rollout discipline.
The payoff can be meaningful: better throughput per vCPU and lower cost per unit of work.
The trade-offs
Arm compatibility still needs proof.
Check native dependencies, third-party agents, language runtimes, container base images, security tooling, observability agents, and any binary packages. A service can pass unit tests and still show different performance behavior under production traffic.
Also avoid assuming all workloads benefit equally. Some workloads are memory-bound, some are network-bound, and some depend on libraries optimized for a different architecture. Benchmark before standardizing.
What to do next
Create a Graviton readiness lane in the platform backlog:
- Identify high-spend compute services with portable runtimes.
- Build multi-architecture container images.
- Run load tests on C9g or C9gd with production-like traffic.
- Compare cost per request, job, or transaction.
- Roll out behind canaries or weighted traffic.
- Track operational differences after the move.
C9g is a good reminder that compute modernization does not always require a rewrite. Sometimes the biggest win is making the same software run better on a better-shaped instance.