Instances›AWS EC2›r5d›r5d.8xlarge
Compute
vCPUs32
Memory256 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Platinum 8175
Clock speed3.1 GHz
Architecturex86_64
Storage
Type2 × 600 GB NVMe SSD
Bandwidth6,800 Mbps
Throughput850 MB/s
IOPS30,000
Networking
Performance10 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
r5d.large2 vCPU · 16 GiB
r5d.xlarge4 vCPU · 32 GiB
r5d.2xlarge8 vCPU · 64 GiB
r5d.4xlarge16 vCPU · 128 GiB
r5d.8xlarge32 vCPU · 256 GiB
r5d.12xlarge48 vCPU · 384 GiB
r5d.16xlarge64 vCPU · 512 GiB
r5d.24xlarge96 vCPU · 768 GiB
r5d.metal96 vCPU · 768 GiB
r5d.8xlarge

r5d.8xlarge is AWS's memory-optimized EC2 size at 32 vCPU and 256 GiB. In the name, "r" stands for RAM, "5" is the generation, "d" marks local NVMe storage and "8xlarge" is the size within the r5d family. It runs on Intel Xeon Platinum 8175 at 3.1 GHz, and AWS introduced it in June 2019. AWS has since shipped r6i, r7i, r8i and r9g; r6i.8xlarge is the direct replacement at this size, scoring 547,219 CoreMark/s against this instance's 467,085 — roughly 17% more throughput for the same vCPU count. The closest Spot shape is mh.vs1.2xlarge at 16 vCPU, so this instance maps to 2 of them — 32 vCPU and 256 GiB across the fleet, $2.30/hr on AWS in US East (N. Virginia), from $0.042/hr on Rackspace Spot. Spot delivers compute as managed Kubernetes, so a node pool of that size is the native shape of the answer rather than a workaround — provided the workload scales horizontally.

Match qualityScale-out match

r5d.8xlarge gives you 32 vCPU and 256 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 2 nodes rather than one.

Spot runs as managed Kubernetes, so a 2-node pool is the normal way to run things rather than a workaround. If your workload already sits behind a load balancer, a queue or a scheduler, it spreads across them without changes. If it needs all 32 cores and 256 GiB in one process, it does not.

No local diskr5d.8xlarge comes with 2 × 600 GB NVMe SSD attached to the machine. Spot nodes use network storage only, so that disk doesn't come with it. If you were using it as fast scratch space, you'd move to a persistent volume or object storage, which are slower to read.
Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$2.304$0.726$1.452$0.995$0.042
$2.262 savings
US Central, Chicagono AWS region$0.042
US Central, Dallasno AWS region$0.262
Hong Kong$2.800$1.764$1.210$0.042
$2.758 savings
Sydney, Australia$2.784$1.128$1.754$1.203$0.042
$2.742 savings
London, UK$2.704$1.195$1.704$1.168$0.262
$2.442 savings
US West, San Jose$2.592$0.773$1.633$1.120$0.004
$2.588 savings
US Central, Dallas 2no AWS region$0.484
When to use it
Good for
  • ●Database instances that keep the working set in RAM
  • ●Graph and search workloads with large indexes
  • ●In-memory caches such as Redis and Memcached
  • ●Workloads that fit inside 256 GiB of RAM
  • ●Jobs that want 2 × 600 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 10 Gigabit
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. r6i.8xlarge is the newer generation at this size.
  • ●The working set needs more than 256 GiB of RAM
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 8.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 32 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
r5d.8xlarge runs $1,682/mo on AWS on-demand. The 2-node equivalent on Rackspace Spot: $31/mo.
  • Spot sells spare capacity at market prices. It is the cheapest compute on the internet.
  • Prices are set by supply and demand. You pay what the market decides.
  • Compute is delivered as fully managed Kubernetes. All infrastructure is taken care of.
  • Egress costs $0.01/GB after the free allowance. AWS charges $0.09/GB.
Build your Cloudspace
Frequently asked questions