Instances›AWS EC2›x2idn›x2idn.24xlarge
Compute
vCPUs96
Memory1536 GiB
Mem / vCPU16.00 GiB
ProcessorXeon Scalable
Clock speed3.5 GHz
Architecturex86_64
Storage
Type2 × 1,425 GB NVMe SSD
Bandwidth60,000 Mbps
Throughput7500 MB/s
IOPS260,000
Networking
Performance75 Gigabit
Max ENIs15
IPv6Yes
GPUNone
Family sizes
x2idn.16xlarge64 vCPU · 1024 GiB
x2idn.24xlarge96 vCPU · 1536 GiB
x2idn.32xlarge128 vCPU · 2048 GiB
x2idn.metal128 vCPU · 2048 GiB
x2idn.24xlarge

x2idn.24xlarge is AWS's memory-optimized EC2 size at 96 vCPU and 1536 GiB. In the name, "x" is the extra-memory line, "2" is the generation, "idn" marks Intel processors, local NVMe storage and enhanced networking and "24xlarge" 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.24xlarge is the direct replacement at this size, scoring 2,202,466 CoreMark/s against this instance's 1,668,912 — roughly 32% more throughput for the same vCPU count. The closest Spot shape is mh.vs1.2xlarge at 16 vCPU, so this instance maps to 11 of them — 176 vCPU and 1408 GiB across the fleet, $10.00/hr on AWS in US East (N. Virginia), from $0.231/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.24xlarge gives you 96 vCPU and 1,536 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 11 nodes rather than one.

Spot runs as managed Kubernetes, so a 11-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 1,536 GiB in one process, it does not.

No local diskx2idn.24xlarge comes with 2 × 1,425 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$10.004$2.849$6.155$3.209$0.231
$9.773 savings
US Central, Chicagono AWS region$0.231
US Central, Dallasno AWS region$1.441
Hong Kong$15.957$9.818$5.118$0.231
$15.726 savings
Sydney, Australia$14.506$2.214$8.925$4.653$0.231
$14.275 savings
London, UK$12.604$2.275$7.756$4.043$1.441
$11.163 savings
US West, San Jose$13.005$4.054$8.002$4.171$0.022
$12.983 savings
US Central, Dallas 2no AWS region$2.662
When to use it
Good for
  • ●In-memory caches such as Redis and Memcached
  • ●Large JVM heaps and application servers that hold state
  • ●OLAP and business intelligence query engines
  • ●Workloads that fit inside 1536 GiB of RAM
  • ●Jobs that want 2 × 1,425 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 75 Gigabit
  • ●Anything that shards cleanly across 11 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 1536 GiB of RAM
  • ●The work is single-threaded. Most of these 96 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 16.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
Stop overpaying AWS. This compute costs $7,303/mo on AWS vs $169/mo on Rackspace Spot.
  • 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