AWS c7g.xlargevsAWS c7gd.large

c7g.xlarge pairs 4 vCPUs with 8GB of RAM at $0.1450/hr On-Demand (about $104/mo at 24×7). c7gd.large pairs 2 vCPUs with 4GB at $0.0907/hr (~$65/mo). c7gd.large is 37% cheaper per hour than c7g.xlarge ($0.0543/hr gap).

Both are generation-7 compute-optimized instances, but they run on different silicon: **c7g.xlarge** is AWS Graviton (ARM64), **c7gd.large** is AWS Graviton (ARM64). AMD variants (suffix `a`) are typically 10% cheaper than Intel siblings at comparable single-thread performance. Graviton variants (suffix `g`) are usually 20–40% cheaper but require ARM64-compatible binaries — most modern Linux stacks are fine, but verify any compiled extensions, native modules, or third-party binaries before migrating. Same vCPU/RAM ratio, same network performance class, different processor.

On raw price-per-performance, the two are c7gd.large delivers ~59% more single-thread Sysbench score per dollar (20876 vs 33264 points per $1/hr). That's the cleanest signal we have for "which one runs your workload faster per dollar," but it only matters if your workload is single-thread-bound; for parallel workloads the multi-core scores (12104 vs 5827) are what to weigh. Spot pricing flips many of these comparisons — when c7g.xlarge drops to $0.0534/hr and c7gd.large drops to $0.0368/hr, the cheap-per-hour winner can swing meaningfully.

In practice, pick c7g.xlarge when your workload is closer to compute-optimized (CPU-bound work — batch processing, web servers under sustained load, game servers). Pick c7gd.large when it's closer to compute-optimized (CPU-bound work — batch processing, web servers under sustained load, game servers). When neither side is obviously right, the cheaper hourly rate usually wins for fault-tolerant batch workloads, while the higher single-core score usually wins for latency-sensitive web traffic. The regional pricing tables linked from each instance page below show where each is currently cheapest — sometimes a >20% regional gap flips the comparison entirely.