AWS r5.8xlargevsAWS r5b.8xlarge

r5.8xlarge pairs 32 vCPUs with 256GB of RAM at $2.0160/hr On-Demand (about $1452/mo at 24×7). r5b.8xlarge pairs 32 vCPUs with 256GB at $2.3840/hr (~$1716/mo). r5.8xlarge is 18% cheaper per hour than r5b.8xlarge ($0.3680/hr gap).

Both are generation-5 memory-optimized instances, but they run on different silicon: **r5.8xlarge** is Intel Xeon (x86_64), **r5b.8xlarge** 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 r5.8xlarge delivers ~18% more single-thread Sysbench score per dollar (525 vs 444 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 (26098 vs 26128) are what to weigh. Spot pricing flips many of these comparisons — when r5.8xlarge drops to $0.4688/hr and r5b.8xlarge drops to $1.0971/hr, the cheap-per-hour winner can swing meaningfully.

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