AWS m5.largevsAWS m5.xlarge

m5.large pairs 2 vCPUs with 8GB of RAM at $0.0960/hr On-Demand (about $69/mo at 24×7). m5.xlarge pairs 4 vCPUs with 16GB at $0.1920/hr (~$138/mo). m5.large is 100% cheaper per hour than m5.xlarge ($0.0960/hr gap).

Because both instances are in the **m5 family**, the only thing that changes between them is sizing — same silicon, same architecture (Intel Xeon (x86_64)), same burstable/sustained behavior. The choice is purely about how much capacity you actually need: m5.large gives you 2 vCPUs and 8GB of RAM, m5.xlarge gives you 4 vCPUs and 16GB. AWS scales pricing close to linearly within a family, so picking the right size is mostly about right-sizing your workload, not getting a better deal per vCPU.

On raw price-per-performance, the two are m5.large delivers ~93% more single-thread Sysbench score per dollar (10615 vs 5500 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 3162) are what to weigh. Spot pricing flips many of these comparisons — when m5.large drops to $0.0363/hr and m5.xlarge drops to $0.0644/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 m5.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.