AWS EC2 Instances›Memory Optimized›r8gb›r8gb.2xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machiner8gb.2xlargemh.vs2.xlarge
vCPU88
Memory64 GiB64 GiB
Local diskNoneNone
On-demand / hr--
Spot / hr--

Compute

vCPUs8
Memory64 GiB
Mem / vCPU8.00 GiB
ProcessorGraviton4 Processor
Clock speed2.8 GHz
Architecturearm64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPSN/A
CoreMark / secN/A

Storage

TypeEBS only
Bandwidth25,000 Mbps
Throughput3125 MB/s
IOPS120,000
Base Bandwidth12,500 Mbps
Base Throughput1562.5 MB/s
Base IOPS60,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

PerformanceUp to 33.33 Gigabit
Max ENIs4
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface38
IPs / ENI15
Baseline Bandwidth16.666 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 typer8gb.2xlarge
Full nameR8GB Double Extra Large
FamilyMemory optimized
Variantr8gb
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2025-09-23
Family sizes

r8gb.2xlarge

The r8gb.2xlarge is a memory-optimized AWS EC2 instance with 8 vCPU and 64 GiB of memory. Rackspace Spot's mh.vs2.xlarge matches it exactly, with 8 vCPU and 64 GiB.

In US East (N. Virginia), Rackspace Spot's on-demand price is about 70% below AWS on-demand and its Spot market price is about 90% below AWS Spot.

Server comparison caveats
x86 substitution

The AWS r8gb.2xlarge is Graviton (arm64). Rackspace Spot does not have arm64 servers, so mh.vs2.xlarge is an x86_64 substitute with similar specs.

You will need x86 builds of your container images. Most software rebuilds without changes, but anything with compiled native code needs a real rebuild rather than a retag. Speed per core also differs between the two chips, so it is worth testing before deciding how many nodes to run.

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$0.729$0.316not offerednot offered$0.217$0.031
$0.512 (70%)
$0.285 (90%)
US Central, Chicagono AWS regionn/an/an/a$0.238$0.011n/an/a
US Central, Dallasno AWS regionn/an/an/a$0.235$0.101n/an/a
Hong Kongnot sold heren/an/an/a$0.242$0.011n/an/a
Sydney, Australianot sold heren/an/an/a$0.254$0.131n/an/a
London, UKnot sold heren/an/an/a$0.218$0.011n/an/a
US West, San Josenot sold heren/an/an/a$0.220$0.001n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$0.220$0.121n/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 64 GiB of RAM
  • ●Parallel work that can occupy 8 vCPU
  • ●Network-heavy services (AWS rates this size at Up to 33.33 Gigabit)
Avoid if
  • ●The working set needs more than 64 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●More than 8.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●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.
r8gb.2xlarge is $532/mo on AWS on-demand and $158/mo on Rackspace Spot on-demand, 70% less. At the Spot market price, the same capacity is $23/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 r8gb.2xlarge cost?

The AWS r8gb.2xlarge costs $0.729/hr on-demand in US East (N. Virginia), about $532/mo running 24/7, or $0.316/hr at the AWS Spot price. On Rackspace Spot, mh.vs2.xlarge is $0.217/hr on-demand, or $0.031/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 r8gb.2xlarge per month?

At 730 hours a month, r8gb.2xlarge in US East (N. Virginia) is $532/mo on AWS on-demand, or $231/mo at the AWS Spot price. The same capacity on Rackspace Spot (mh.vs2.xlarge) is $158/mo on-demand, or $23/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

What is the Rackspace Spot equivalent of r8gb.2xlarge?

mh.vs2.xlarge, at 8 vCPU and 64 GiB, with the same vCPU count and the same memory against r8gb.2xlarge. In US East (N. Virginia), Rackspace Spot's on-demand price is about 70% below AWS on-demand and its Spot market price is about 90% below AWS Spot. Rackspace Spot classes are region-suffixed, so the exact name differs per row.

Is r8gb.2xlarge ARM or x86?

ARM. r8gb.2xlarge runs on AWS Graviton4 Processor, so its binaries and container images are aarch64. Rackspace Spot's mh.vs2.xlarge is x86-64, which means this is a substitution and not a migration: anything not already built multi-arch has to be rebuilt before it runs. For interpreted stacks that is usually a rebuild of the base image; for anything with native extensions, check them individually.

What is the difference between r8gb and r9g?

r9g is the newer generation. It runs on AWS Graviton5 Processor against r8gb's AWS Graviton4 Processor. On-demand in US East (N. Virginia) the newer size is 30% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.

What is a cheaper alternative to r8gb.2xlarge?

Rackspace Spot mh.vs2.xlarge (8 vCPU, 64 GiB) is $158/mo on-demand or $23/mo at the Spot price, against $532/mo on-demand or $231/mo at the Spot price for r8gb.2xlarge 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.