AWS m5.xlargevsAWS m6id.xlarge

m5.xlarge pairs 4 vCPUs with 16GB of RAM at $0.1920/hr On-Demand (about $138/mo at 24×7). m6id.xlarge pairs 4 vCPUs with 16GB at $0.2373/hr (~$171/mo). m5.xlarge is 24% cheaper per hour than m6id.xlarge ($0.0453/hr gap).

These are different generations of the same series. **m6id.xlarge** is the newer generation, and AWS's pattern across generations is fairly consistent: ~10–15% better single-thread, 15–30% better multi-core, and similar or modestly higher per-hour pricing — so the price/performance per dollar usually improves with each generation. **m5.xlarge** is still available and still works (AWS doesn't retire instance types quickly), but for new workloads the newer generation is typically the better default unless you have a specific reason to pin to the older AMI or there's a meaningful regional pricing advantage today.

On raw price-per-performance, the two are m6id.xlarge delivers ~128% more single-thread Sysbench score per dollar (5500 vs 12554 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 (3162 vs 6175) are what to weigh. Spot pricing flips many of these comparisons — when m5.xlarge drops to $0.0626/hr and m6id.xlarge drops to $0.0799/hr, the cheap-per-hour winner can swing meaningfully.

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