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

Compared with Rackspace Spot

AWSRackspace Spot
Machiner8i.16xlarge4 × mh.vs1.2xlarge
vCPU6464
Memory512 GiB512 GiB
Local diskNoneNone
On-demand / hr$4.445$1.724
Spot / hr$1.677$0.084
Prices in US East, N. Virginia

Compute

vCPUs64
Memory512 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS283
CoreMark / sec1,615,754

Storage

TypeEBS only
Bandwidth20,000 Mbps
Throughput2500 MB/s
IOPS80,000
Base Bandwidth20,000 Mbps
Base Throughput2500 MB/s
Base IOPS80,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance30 Gigabit
Max ENIs16
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface106
IPs / ENI64
Baseline Bandwidth30 Gbps

NUMA Architecture

Uses NUMANo
Node CountN/A
Max DistanceN/A
Cores / NodeN/A
Threads / NodeN/A
Memory / NodeN/A
L3 Cache / NodeN/A
L3 Cache SharedN/A

AWS Metadata

Instance typer8i.16xlarge
Full nameR8I 16xlarge Extra Large
FamilyMemory optimized
Variantr8i
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2025-08-19
Family sizes

r8i.16xlarge

The r8i.16xlarge is a memory-optimized AWS EC2 instance with 64 vCPU and 512 GiB of memory. In US East (N. Virginia), the closest Rackspace Spot server is mh.vs1.2xlarge at 16 vCPU and 128 GiB, so you will need 4 of them to get a total of 64 vCPU and 512 GiB.

Even with 4 servers, Rackspace Spot's on-demand price is about 61% below AWS on-demand and its Spot market price is about 95% 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 r8i.16xlarge gives you 64 vCPU and 512 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 4 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 4 servers without changes. If it needs all 64 cores and 512 GiB in one process, it does not.

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$4.445$1.677not offerednot offered$1.724$0.084
$2.721 (61%)
$1.593 (95%)
US Central, Chicagono AWS regionn/an/an/a$1.856$0.084n/an/a
US Central, Dallasno AWS regionn/an/an/a$1.852$0.524n/an/a
Hong Kongnot sold heren/an/an/a$1.976$0.084n/an/a
Sydney, Australia$5.327$2.272not offerednot offered$1.964$0.764
$3.363 (63%)
$1.508 (66%)
London, UK$5.221$2.337not offerednot offered$1.680$0.116
$3.541 (68%)
$2.221 (95%)
US West, San Jose$4.939$1.363not offerednot offered$1.760$0.008
$3.179 (64%)
$1.355 (99%)
US Central, Dallas 2no AWS regionn/an/an/a$1.760$0.968n/an/a

Prices updated 17 Nov 2026.

When to use it

Good for
  • ●Graph and search workloads with large indexes
  • ●In-memory caches such as Redis and Memcached
  • ●Large JVM heaps and application servers that hold state
  • ●Workloads that fit inside 512 GiB of RAM
  • ●Parallel work that can occupy 64 vCPU
  • ●Network-heavy services (AWS rates this size at 30 Gigabit)
  • ●Anything that shards cleanly across 4 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 512 GiB of RAM
  • ●The work is single-threaded. Most of these 64 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 8.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
r8i.16xlarge is $3,245/mo on AWS on-demand and $1,259/mo on Rackspace Spot on-demand for 4 servers, 61% less. At the Spot market price, the same capacity is $61/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 r8i.16xlarge cost?

The AWS r8i.16xlarge costs $4.45/hr on-demand in US East (N. Virginia), about $3,245/mo running 24/7, or $1.68/hr at the AWS Spot price. On Rackspace Spot, 4 × mh.vs1.2xlarge is $1.72/hr on-demand, or $0.084/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 r8i.16xlarge per month?

At 730 hours a month, r8i.16xlarge in US East (N. Virginia) is $3,245/mo on AWS on-demand, or $1,224/mo at the AWS Spot price. The same capacity on Rackspace Spot (4 × mh.vs1.2xlarge) is $1,259/mo on-demand, or $61/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 r8i.16xlarge?

4. 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 512 GiB takes 4 of them: 64 vCPU and 512 GiB in total. Per-region fleet sizes differ and are shown in the table.

What is the difference between r8i and r9g?

r9g is the newer generation. It runs on AWS Graviton5 Processor against r8i's Intel Xeon Scalable (Granite Rapids). On-demand in US East (N. Virginia) the newer size is 8% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.

What is a cheaper alternative to r8i.16xlarge?

Rackspace Spot 4 × mh.vs1.2xlarge (64 vCPU, 512 GiB) is $1,259/mo on-demand or $61/mo at the Spot price, against $3,245/mo on-demand or $1,224/mo at the Spot price for r8i.16xlarge on AWS in US East (N. Virginia). The trade is real: Rackspace Spot capacity is priced by demand and can be reclaimed when demand rises, and workloads have to be containerized.