AWS EC2 Instances›Memory Optimized›r8in›r8in.metal-96xl

Compared with Rackspace Spot

AWSRackspace Spot
Machiner8in.metal-96xl24 × mh.vs1.2xlarge
vCPU384384
Memory3072 GiB3072 GiB
Local diskNoneNone
On-demand / hr$40.166$10.344
Spot / hr$7.098$0.504
Prices in US East, N. Virginia

Compute

vCPUs384
Memory3072 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS246
CoreMark / sec9,103,841

Storage

TypeEBS only
Bandwidth120,000 Mbps
Throughput15000 MB/s
IOPS480,000
Base Bandwidth120,000 Mbps
Base Throughput15000 MB/s
Base IOPS480,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance600 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingNo
Branch Interface0
IPs / ENI64
Baseline Bandwidth300 Gbps

NUMA Architecture

Uses NUMAYes
Node Count6
Max Distance28
Cores / Node32
Threads / Node64
Memory / Node516,013 MB
L3 Cache / Node480 MB
L3 Cache SharedYes

AWS Metadata

Instance typer8in.metal-96xl
Full nameR8IN Metal-96xl
FamilyMemory optimized
Variantr8in
GenerationCurrent
Bare MetalNo
EMR supportNo
DedicatedSupported
Introduced2026-06-09
Family sizes

r8in.metal-96xl

r8in.metal-96xl is AWS's memory-optimized EC2 size at 384 vCPU and 3072 GiB. Rackspace Spot's largest server is 16 vCPU and 128 GiB, so matching this instance would take 24 × 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 r8in.metal-96xl is 384 vCPU and 3,072 GiB. The largest comparable Rackspace Spot server is mh.vs1.2xlarge at 16 vCPU and 128 GiB, so matching it would take 24 of them. That maths works out, but 24 nodes is a redesign rather than a migration, because a single block of 3,072 GiB does not survive being split across a network.

If you chose r8in.metal-96xl because the work genuinely needs 384 cores and 3,072 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.

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$40.166$7.098not offerednot offered$10.344$0.504
$29.822 (74%)
$6.594 (93%)
US Central, Chicagono AWS regionn/an/an/a$11.136$0.504n/an/a
US Central, Dallasno AWS regionn/an/an/a$11.112$3.144n/an/a
Hong Kongnot sold heren/an/an/a$11.856$0.504n/an/a
Sydney, Australianot sold heren/an/an/a$11.784$4.584n/an/a
London, UKnot sold heren/an/an/a$10.080$0.696n/an/a
US West, San Josenot sold heren/an/an/a$10.560$0.048n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$10.560$5.808n/an/a

Prices updated 17 Nov 2026.

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 3072 GiB of RAM
  • ●Parallel work that can occupy 384 vCPU
  • ●Network-heavy services (AWS rates this size at 600 Gigabit)
Avoid if
  • ●The working set needs more than 3072 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 8.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 384 vCPU would sit idle.
r8in.metal-96xl is $29,321/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 r8in.metal-96xl cost?

The AWS r8in.metal-96xl costs $40.17/hr on-demand in US East (N. Virginia), about $29,321/mo running 24/7, or $7.10/hr at the AWS Spot price. On Rackspace Spot, 24 × mh.vs1.2xlarge is $10.34/hr on-demand, or $0.504/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 r8in.metal-96xl per month?

At 730 hours a month, r8in.metal-96xl in US East (N. Virginia) is $29,321/mo on AWS on-demand, or $5,181/mo at the AWS Spot price. The same capacity on Rackspace Spot (24 × mh.vs1.2xlarge) is $7,551/mo on-demand, or $368/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 r8in.metal-96xl with Rackspace Spot?

Not as a single machine. Rackspace Spot's largest VM shape is 16 vCPU and 128 GiB, so it would take 24 × mh.vs1.2xlarge to reach 384 vCPU and 3072 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 24-node fleet.

What is a cheaper alternative to r8in.metal-96xl?

Rackspace Spot 24 × mh.vs1.2xlarge (384 vCPU, 3072 GiB) is $7,551/mo on-demand or $368/mo at the Spot price, against $29,321/mo on-demand or $5,181/mo at the Spot price for r8in.metal-96xl 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.