The r5ad.16xlarge is a memory-optimized AWS EC2 instance: 64 vCPU and 512 GiB of memory, 8.00 GiB per vCPU. In the name, "r" stands for RAM, "5" is the generation, "ad" marks AMD processors and local NVMe storage and "16xlarge" is the size within the r5ad family. It runs on AMD EPYC 7571 at 2.5 GHz, and AWS introduced it in March 2019. AWS has since shipped r6i, r7i, r8i and r9g; r6i.16xlarge is the direct replacement at this size, scoring 1,080,078 CoreMark/s against this instance's 824,530 — roughly 31% more throughput for the same vCPU count. No single Spot node covers 64 vCPU and 512 GiB, so the equivalent is a fleet: 4 × mh.vs1.2xlarge, 64 vCPU and 512 GiB in total, $4.19/hr on AWS in US East (N. Virginia), from $0.084/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
r5ad.16xlarge gives you 64 vCPU and 512 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 4 nodes rather than one.
Spot runs as managed Kubernetes, so a 4-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 64 cores and 512 GiB in one process, it does not.
No local diskr5ad.16xlarge comes with 4 × 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.
