AWS EC2 Instances›Memory Optimized›x1e›x1e.32xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinex1e.32xlarge28 × mh.vs1.2xlarge
vCPU128448
Memory3904 GiB3584 GiB
Local disk2 × 1,920 GB SSDNone
On-demand / hr$26.688$12.068
Spot / hr$3.745$0.588
Prices in US East, N. Virginia

Compute

vCPUs128
Memory3904 GiB
Mem / vCPU30.50 GiB
ProcessorHigh Frequency Intel Xeon E7-8880 v3
Clock speed2.3 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS247
CoreMark / sec2,226,377

Storage

Type2 × 1,920 GB SSD
Bandwidth14,000 Mbps
Throughput1750 MB/s
IOPS80,000
Base Bandwidth14,000 Mbps
Base Throughput1750 MB/s
Base IOPS80,000
Devices2
NVMe DriveNo
SSDYes
Swap PartitionNo

Networking

Performance25 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingNo
Branch Interface0
IPs / ENI30
Baseline Bandwidth25 Gbps

NUMA Architecture

Uses NUMAYes
Node Count4
Max Distance21
Cores / Node16
Threads / Node32
Memory / Node983,769.5 MB
L3 Cache / Node45 MB
L3 Cache SharedYes

AWS Metadata

Instance typex1e.32xlarge
Full nameX1E 32xlarge
FamilyMemory optimized
Variantx1e
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2017-09-13
Family sizes

x1e.32xlarge

AWS's x1e.32xlarge is a memory-optimized instance with 128 vCPU and 3904 GiB. Rackspace Spot's largest server is 16 vCPU and 128 GiB, so matching this instance would take 28 × mh.vs1.2xlarge. That is arithmetically true and operationally absurd.

The Rackspace 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 server.

Server comparison caveats
No single-node equivalent

The AWS x1e.32xlarge is 128 vCPU and 3,904 GiB. The largest comparable Rackspace Spot server 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, because 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 disk

The AWS x1e.32xlarge comes with 2 × 1,920 GB SSD attached to the machine. Rackspace Spot servers 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 attached to your Rackspace Spot server, or object storage, and both are slower to read.

Pricing by region

1 hr

Regions are Rackspace Spot locations.

RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace on-demandRackspace SpotOn-demand price savingsSpot price savings
US East, N. Virginia$26.688$3.745$16.446$8.579$12.068$0.588
$14.620 (55%)
$3.157 (84%)
US Central, Chicagono AWS regionn/an/an/a$12.992$0.588n/an/a
US Central, Dallasno AWS regionn/an/an/a$12.964$3.668n/an/a
Hong Kongnot sold heren/an/an/a$13.832$0.588n/an/a
Sydney, Australia$38.688$5.525$23.839$12.437$13.748$5.348
$24.940 (64%)
$0.177 (3%)
London, UKnot sold heren/an/an/a$11.760$0.812n/an/a
US West, San Josenot sold heren/an/an/a$12.320$0.056n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$12.320$6.776n/an/a

Prices updated 18 Nov 2026.

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 Rackspace 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, since that ratio is fixed for the whole family
x1e.32xlarge is $19,482/mo on AWS on-demand. A single mh.vs1.2xlarge is $315/mo on Rackspace Spot on-demand. At this size the per-server price is the honest comparison.
  • Rackspace 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

How much does x1e.32xlarge cost?

The AWS x1e.32xlarge costs $26.69/hr on-demand in US East (N. Virginia), about $19,482/mo running 24/7, or $3.75/hr at the AWS Spot price. On Rackspace Spot, 28 × mh.vs1.2xlarge is $12.07/hr on-demand, or $0.588/hr at the Spot price. Rackspace Spot also sells in Chicago and Dallas, where AWS operates no region at all, so those rows have no AWS price to compare against.

How much is x1e.32xlarge per month?

At 730 hours a month, x1e.32xlarge in US East (N. Virginia) is $19,482/mo on AWS on-demand, or $2,734/mo at the AWS Spot price. The same capacity on Rackspace Spot (28 × mh.vs1.2xlarge) is $8,810/mo on-demand, or $429/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

Can I replace x1e.32xlarge with Rackspace Spot?

Not as a single machine. Rackspace Spot's largest VM shape is 16 vCPU and 128 GiB, so it would take 28 × mh.vs1.2xlarge to reach 128 vCPU and 3904 GiB, and past roughly twenty nodes that stops being a credible substitution. Where the workload does shard (batch, web, queue consumers), a single mh.vs1.2xlarge at $0.021/hr is the number to compare against; the table's Rackspace Spot column prices the full 28-node fleet.

Does the Rackspace Spot equivalent include local NVMe storage?

No. x1e.32xlarge ships 2 × 1,920 GB of local SSD. Rackspace Spot servers are network-backed, so a workload that leans on local disk throughput needs block storage or a re-architecture. Everything else about the match still holds.

Is x1e.32xlarge still worth using?

For workloads already running on it, yes: it works and it is priced accordingly. For anything new, x2idn.32xlarge is the current answer. 2 newer generations of the x family have shipped since (x2gd and x8i), which is the signal that matters for infrastructure you expect to keep running.

What is the difference between x1e and x2idn?

x2idn is the newer generation. It runs on Intel Xeon Scalable (Icelake) against x1e's High Frequency Intel Xeon E7-8880 v3 (Haswell). On-demand in US East (N. Virginia) the newer size is 50% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.