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

Compared with Rackspace Spot

AWSRackspace Spot
Machiner8i.8xlarge2 × mh.vs1.2xlarge
vCPU3232
Memory256 GiB256 GiB
Local diskNoneNone
On-demand / hr$2.223$0.862
Spot / hr$0.612$0.042
Prices in US East, N. Virginia

Compute

vCPUs32
Memory256 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS243
CoreMark / sec759,073

Storage

TypeEBS only
Bandwidth10,000 Mbps
Throughput1250 MB/s
IOPS40,000
Base Bandwidth10,000 Mbps
Base Throughput1250 MB/s
Base IOPS40,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance15 Gigabit
Max ENIs10
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface82
IPs / ENI50
Baseline Bandwidth15 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.8xlarge
Full nameR8I Eight Extra Large
FamilyMemory optimized
Variantr8i
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2025-08-19
Family sizes

r8i.8xlarge

The r8i.8xlarge is a memory-optimized AWS EC2 instance with 32 vCPU and 256 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 2 of them to get a total of 32 vCPU and 256 GiB.

Even with 2 servers, Rackspace Spot's on-demand price is about 61% below AWS on-demand and its Spot market price is about 93% 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.8xlarge gives you 32 vCPU and 256 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 2 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 2 servers without changes. If it needs all 32 cores and 256 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$2.223$0.612not offerednot offered$0.862$0.042
$1.361 (61%)
$0.570 (93%)
US Central, Chicagono AWS regionn/an/an/a$0.928$0.042n/an/a
US Central, Dallasno AWS regionn/an/an/a$0.926$0.262n/an/a
Hong Kongnot sold heren/an/an/a$0.988$0.042n/an/a
Sydney, Australia$2.664$1.201not offerednot offered$0.982$0.382
$1.682 (63%)
$0.819 (68%)
London, UK$2.611$0.849not offerednot offered$0.840$0.058
$1.771 (68%)
$0.791 (93%)
US West, San Jose$2.470$0.996not offerednot offered$0.880$0.004
$1.590 (64%)
$0.992 (100%)
US Central, Dallas 2no AWS regionn/an/an/a$0.880$0.484n/an/a

Prices updated 18 Nov 2026.

When to use it

Good for
  • ●OLAP and business intelligence query engines
  • ●Real-time analytics over hot datasets
  • ●Database instances that keep the working set in RAM
  • ●Workloads that fit inside 256 GiB of RAM
  • ●Parallel work that can occupy 32 vCPU
  • ●Network-heavy services (AWS rates this size at 15 Gigabit)
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 256 GiB of RAM
  • ●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 32 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
r8i.8xlarge is $1,623/mo on AWS on-demand and $629/mo on Rackspace Spot on-demand for 2 servers, 61% less. At the Spot market price, the same capacity is $31/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.8xlarge cost?

The AWS r8i.8xlarge costs $2.22/hr on-demand in US East (N. Virginia), about $1,623/mo running 24/7, or $0.612/hr at the AWS Spot price. On Rackspace Spot, 2 × mh.vs1.2xlarge is $0.862/hr on-demand, or $0.042/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.8xlarge per month?

At 730 hours a month, r8i.8xlarge in US East (N. Virginia) is $1,623/mo on AWS on-demand, or $446/mo at the AWS Spot price. The same capacity on Rackspace Spot (2 × mh.vs1.2xlarge) is $629/mo on-demand, or $31/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.8xlarge?

2. 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 32 vCPU and 256 GiB takes 2 of them: 32 vCPU and 256 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.8xlarge?

Rackspace Spot 2 × mh.vs1.2xlarge (32 vCPU, 256 GiB) is $629/mo on-demand or $31/mo at the Spot price, against $1,623/mo on-demand or $446/mo at the Spot price for r8i.8xlarge 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.