AWS m5.largevsAWS m5d.large

m5.large pairs 2 vCPUs with 8GB of RAM at $0.0960/hr On-Demand (about $69/mo at 24×7). m5d.large pairs 2 vCPUs with 8GB at $0.1130/hr (~$81/mo). m5.large is 18% cheaper per hour than m5d.large ($0.0170/hr gap).

Both are generation-5 general-purpose instances, but they run on different silicon: **m5.large** is Intel Xeon (x86_64), **m5d.large** is Intel Xeon (x86_64). 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 m5.large delivers ~13% more single-thread Sysbench score per dollar (10615 vs 9416 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 (1503 vs 1589) are what to weigh. Spot pricing flips many of these comparisons — when m5.large drops to $0.0363/hr and m5d.large drops to $0.0536/hr, the cheap-per-hour winner can swing meaningfully.

In practice, pick m5.large when your workload is closer to general-purpose (balanced general-purpose workloads with a 1:4 vCPU-to-memory ratio). Pick m5d.large when it's closer to general-purpose (balanced general-purpose workloads with a 1:4 vCPU-to-memory ratio). 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.