AWS EC2 Instances›Memory Optimized›x1›x1.16xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinex1.16xlarge7 × mh.vs1.2xlarge
vCPU64112
Memory976 GiB896 GiB
Local disk1 × 1,920 GB SSDNone
On-demand / hr$6.669$3.017
Spot / hr$1.559$0.147
Prices in US East, N. Virginia

Compute

vCPUs64
Memory976 GiB
Mem / vCPU15.25 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 FPS213
CoreMark / sec1,144,390

Storage

Type1 × 1,920 GB SSD
Bandwidth7,000 Mbps
Throughput875 MB/s
IOPS40,000
Base Bandwidth7,000 Mbps
Base Throughput875 MB/s
Base IOPS40,000
Devices1
NVMe DriveNo
SSDYes
Swap PartitionNo

Networking

Performance10 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingNo
Branch Interface0
IPs / ENI30
Baseline Bandwidth10 Gbps

NUMA Architecture

Uses NUMAYes
Node Count2
Max Distance21
Cores / Node16
Threads / Node32
Memory / Node491,829 MB
L3 Cache / Node45 MB
L3 Cache SharedYes

AWS Metadata

Instance typex1.16xlarge
Full nameX1 Extra High-Memory 16xlarge Extra Large
FamilyMemory optimized
Variantx1
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2016-10-10
Family sizes
x1.16xlarge64 vCPU · 976 GiB
x1.32xlarge128 vCPU · 1952 GiB

x1.16xlarge

AWS's x1.16xlarge is a memory-optimized instance with 64 vCPU and 976 GiB. In US East (N. Virginia), the closest Rackspace Spot server is mh.vs1.2xlarge at 16 vCPU and 128 GiB, so you will need 7 of them to get a total of 112 vCPU and 896 GiB.

Even with 7 servers, Rackspace Spot's on-demand price is about 55% below AWS on-demand and its Spot market price is about 91% below AWS Spot. Rackspace Spot offers managed Kubernetes, so you can run them together in one cluster.

Server comparison caveats
Scale-out match

The AWS x1.16xlarge gives you 64 vCPU and 976 GiB in a single machine. The largest comparable Rackspace Spot server, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 7 servers rather than one.

This setup works best for Kubernetes workloads, or for workloads that already sit behind a load balancer, a queue or a scheduler, because they spread across the 7 servers without changes. If it needs all 64 cores and 976 GiB in one process, it does not.

No local disk

The AWS x1.16xlarge comes with 1 × 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$6.669$1.559$4.110$2.144$3.017$0.147
$3.652 (55%)
$1.412 (91%)
US Central, Chicagono AWS regionn/an/an/a$3.248$0.147n/an/a
US Central, Dallasno AWS regionn/an/an/a$3.241$0.917n/an/a
Hong Kong$10.638$2.872$6.555$3.419$3.458$0.147
$7.180 (67%)
$2.725 (95%)
Sydney, Australia$9.671$1.268$5.959$3.109$3.437$1.337
$6.234 (64%)
AWS cheaper
London, UK$8.403$1.126$5.179$2.701$2.940$0.203
$5.463 (65%)
$0.923 (82%)
US West, San Josenot sold heren/an/an/a$3.080$0.014n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$3.080$1.694n/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 976 GiB of RAM
  • ●Jobs that want 1 × 1,920 GB of local SSD scratch space
  • ●Network-heavy services (AWS rates this size at 10 Gigabit)
  • ●Anything that shards cleanly across 7 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. x2gd.16xlarge is the newer generation at this size.
  • ●The working set needs more than 976 GiB of RAM
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 15.25 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 64 vCPU would sit idle.
x1.16xlarge is $4,868/mo on AWS on-demand and $2,202/mo on Rackspace Spot on-demand for 7 servers, 55% less. At the Spot market price, the same capacity is $107/mo.
  • 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 x1.16xlarge cost?

The AWS x1.16xlarge costs $6.67/hr on-demand in US East (N. Virginia), about $4,868/mo running 24/7, or $1.56/hr at the AWS Spot price. On Rackspace Spot, 7 × mh.vs1.2xlarge is $3.02/hr on-demand, or $0.147/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 x1.16xlarge per month?

At 730 hours a month, x1.16xlarge in US East (N. Virginia) is $4,868/mo on AWS on-demand, or $1,138/mo at the AWS Spot price. The same capacity on Rackspace Spot (7 × mh.vs1.2xlarge) is $2,202/mo on-demand, or $107/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

How many Rackspace Spot nodes replace one x1.16xlarge?

7. The mh.vs1.2xlarge server is 16 vCPU and 128 GiB, and Rackspace Spot's whole VM catalog tops out at 16 vCPU, so covering 64 vCPU and 976 GiB takes 7 of them: 112 vCPU and 896 GiB in total. Per-region fleet sizes differ and are shown in the table.

Does the Rackspace Spot equivalent include local NVMe storage?

No. x1.16xlarge ships 1 × 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 x1.16xlarge still worth using?

For workloads already running on it, yes: it works and it is priced accordingly. For anything new, x2gd.16xlarge is the current answer and measures roughly 11% more CoreMark throughput at the same vCPU count. 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 x1 and x2gd?

x2gd is the newer generation. It runs on AWS Graviton2 Processor against x1's High Frequency Intel Xeon E7-8880 v3 (Haswell). On the CoreMark figures in this dataset, x2gd.16xlarge scores 1,269,505 per second against x1.16xlarge's 1,144,390. On-demand in US East (N. Virginia) the newer size is 20% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.