The i3en.24xlarge is a storage-optimized AWS EC2 instance: 96 vCPU and 768 GiB of memory, 8.00 GiB per vCPU. In the name, "i" is I/O, meaning local storage, "3" is the generation, "en" marks extended capacity and enhanced networking and "24xlarge" is the size within the i3en family. It runs on Intel Xeon Platinum 8175 at 3.1 GHz, and AWS introduced it in May 2019. AWS has since shipped i4i, i7i and i8g; i4i.24xlarge is the direct replacement at this size, scoring 1,713,980 CoreMark/s against this instance's 1,364,606 — roughly 26% more throughput for the same vCPU count. No single Spot node covers 96 vCPU and 768 GiB, so the equivalent is a fleet: 6 × mh.vs1.2xlarge, 96 vCPU and 768 GiB in total, $10.85/hr on AWS in US East (N. Virginia), from $0.126/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
i3en.24xlarge gives you 96 vCPU and 768 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 6 nodes rather than one.
Spot runs as managed Kubernetes, so a 6-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 96 cores and 768 GiB in one process, it does not.
No local diski3en.24xlarge comes with 8 × 7,500 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.
