Instances›AWS EC2›x1e›x1e.32xlarge
Compute
vCPUs128
Memory3904 GiB
Mem / vCPU30.50 GiB
ProcessorHigh Frequency Intel Xeon E7-8880 v3
Clock speed2.3 GHz
Architecturex86_64
Storage
Type2 × 1,920 GB SSD
Bandwidth14,000 Mbps
Throughput1750 MB/s
IOPS80,000
Networking
Performance25 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
x1e.xlarge4 vCPU · 122 GiB
x1e.2xlarge8 vCPU · 244 GiB
x1e.4xlarge16 vCPU · 488 GiB
x1e.8xlarge32 vCPU · 976 GiB
x1e.16xlarge64 vCPU · 1952 GiB
x1e.32xlarge128 vCPU · 3904 GiB
x1e.32xlarge

The x1e.32xlarge pairs 128 vCPU with 3904 GiB of RAM, the 30.50 GiB-per-vCPU ratio that marks a memory-optimized instance. In the name, "x" is the extra-memory line, "1" is the generation, "e" marks extended capacity and "32xlarge" is the size within the x1e family. It runs on High Frequency Intel Xeon E7-8880 v3 (Haswell) at 2.3 GHz, and AWS introduced it in September 2017. AWS has since shipped x2gd and x8i; x2idn.32xlarge is the direct replacement at this size. Spot's largest VM is 16 vCPU and 128 GiB, so matching this instance would take 28 × mh.vs1.2xlarge — arithmetically true and operationally absurd. The Spot column below prices that whole fleet, so read it as a scale reference rather than a drop-in replacement: at this size the useful question is what a shard of the workload costs, which is $0.021/hr per node.

Match qualityNo single-node equivalent

x1e.32xlarge is 128 vCPU and 3,904 GiB. The largest comparable Spot node is mh.vs1.2xlarge at 16 vCPU and 128 GiB, so matching it would take 28 of them. That maths works out, but 28 nodes is a redesign rather than a migration — a single block of 3,904 GiB does not survive being split across a network.

If you chose x1e.32xlarge because the work genuinely needs 128 cores and 3,904 GiB together — an in-memory database, a large analytics engine, a single big solver — Rackspace Spot has no equivalent. What does fit is everything around it: the application servers, batch workers and CI that talk to that machine, which is usually the larger share of the bill.

No local diskx1e.32xlarge comes with 2 × 1,920 GB 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$26.688$3.574$16.446$8.579$0.588
$26.100 savings
US Central, Chicagono AWS region$0.588
US Central, Dallasno AWS region$3.668
Hong Kong$0.588
Sydney, Australia$38.688$3.869$23.839$12.437$0.588
$38.100 savings
London, UK$3.668
US West, San Jose$0.056
US Central, Dallas 2no AWS region$6.776
When to use it
Good for
  • ●Database instances that keep the working set in RAM
  • ●Graph and search workloads with large indexes
  • ●In-memory caches such as Redis and Memcached
  • ●Workloads that fit inside 3904 GiB of RAM
  • ●Jobs that want 2 × 1,920 GB of local SSD scratch space
  • ●Network-heavy services — AWS rates this size at 25 Gigabit
Avoid if
  • ●Starting a new deployment. x2idn.32xlarge is the newer generation at this size.
  • ●The working set needs more than 3904 GiB of RAM
  • ●You want a single-machine Spot equivalent. At this size there is not one.
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 30.50 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
x1e.32xlarge is $19,482/mo on AWS on-demand. A mh.vs1.2xlarge node on Rackspace Spot is $15/mo — at this size the per-node price is the honest comparison.
  • 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