The m5ad.16xlarge pairs 64 vCPU with 256 GiB of RAM, the 4.00 GiB-per-vCPU ratio that marks a general-purpose instance. In the name, "m" is the general-purpose line, "5" is the generation, "ad" marks AMD processors and local NVMe storage and "16xlarge" is the size within the m5ad family. It runs on AMD EPYC 7571 at 2.5 GHz, and AWS introduced it in March 2019. AWS has since shipped m6i, m7i, m8i and m9g; m6i.16xlarge is the direct replacement at this size, scoring 1,069,742 CoreMark/s against this instance's 818,519 — roughly 31% more throughput for the same vCPU count. Spot's node ladder tops out below this size, so m5ad.16xlarge becomes 4 × gp.vs1.2xlarge (64 vCPU, 256 GiB combined), about 95% below the US East (N. Virginia) on-demand rate. 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
m5ad.16xlarge gives you 64 vCPU and 256 GiB in a single machine. The largest comparable Spot node, gp.vs1.2xlarge, is 16 vCPU and 64 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 256 GiB in one process, it does not.
No local diskm5ad.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.
