The x2idn.16xlarge pairs 64 vCPU with 1024 GiB of RAM, the 16.00 GiB-per-vCPU ratio that marks a memory-optimized instance. In the name, "x" is the extra-memory line, "2" is the generation, "idn" marks Intel processors, local NVMe storage and enhanced networking and "16xlarge" is the size within the x2idn family. It runs on Intel Xeon Scalable (Icelake) at 3.5 GHz, and AWS introduced it in March 2022. AWS has since shipped x8i; x8i.16xlarge is the direct replacement at this size, scoring 1,603,206 CoreMark/s against this instance's 1,098,335 — roughly 46% more throughput for the same vCPU count. Spot's node ladder tops out below this size, so x2idn.16xlarge becomes 8 × mh.vs1.2xlarge (128 vCPU, 1024 GiB combined), $6.67/hr on AWS in US East (N. Virginia), from $0.168/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
x2idn.16xlarge gives you 64 vCPU and 1,024 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 8 nodes rather than one.
Spot runs as managed Kubernetes, so a 8-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 1,024 GiB in one process, it does not.
No local diskx2idn.16xlarge comes with 1 × 1,900 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.
