AWS r7g.largevsAWS r7g.xlarge

r7g.large pairs 2 vCPUs with 16GB of RAM at $0.1071/hr On-Demand (about $77/mo at 24×7). r7g.xlarge pairs 4 vCPUs with 32GB at $0.2142/hr (~$154/mo). r7g.large is 100% cheaper per hour than r7g.xlarge ($0.1071/hr gap).

Because both instances are in the **r7g family**, the only thing that changes between them is sizing — same silicon, same architecture (AWS Graviton (ARM64)), same burstable/sustained behavior. The choice is purely about how much capacity you actually need: r7g.large gives you 2 vCPUs and 16GB of RAM, r7g.xlarge gives you 4 vCPUs and 32GB. 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 r7g.large delivers ~100% more single-thread Sysbench score per dollar (28161 vs 14085 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 (5811 vs 11824) are what to weigh. Spot pricing flips many of these comparisons — when r7g.large drops to $0.0401/hr and r7g.xlarge drops to $0.0634/hr, the cheap-per-hour winner can swing meaningfully.

In practice, pick r7g.large when your workload is closer to memory-optimized (memory-bound work — in-memory databases, real-time analytics, large caches). Pick r7g.xlarge when it's closer to memory-optimized (memory-bound work — in-memory databases, real-time analytics, large caches). 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.