AWS EC2 Instances›General Purpose›m5ad›m5ad.8xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinem5ad.8xlarge2 × gp.vs1.2xlarge
vCPU3232
Memory128 GiB128 GiB
Local disk2 × 600 GB NVMe SSDNone
On-demand / hr$1.648$0.608
Spot / hr$0.616$0.082
Prices in US East, N. Virginia

Compute

vCPUs32
Memory128 GiB
Mem / vCPU4.00 GiB
ProcessorEPYC 7571
Clock speed2.5 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS101
CoreMark / sec386,551

Storage

Type2 × 600 GB NVMe SSD
Bandwidth4,750 Mbps
Throughput593.75 MB/s
IOPS20,000
Base Bandwidth4,750 Mbps
Base Throughput593.75 MB/s
Base IOPS20,000
Devices2
NVMe DriveYes
SSDYes
Swap PartitionNo
Local Read IOPS466,666
Local Write IOPS233,334

Networking

PerformanceUp to 10 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface54
IPs / ENI30
Baseline Bandwidth7.5 Gbps

NUMA Architecture

Uses NUMAYes
Node Count2
Max Distance16
Cores / Node8
Threads / Node16
Memory / Node63,407 MB
L3 Cache / Node16 MB
L3 Cache SharedYes

AWS Metadata

Instance typem5ad.8xlarge
Full nameM5AD Eight Extra Large
FamilyGeneral purpose
Variantm5ad
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedN/A
Introduced2019-03-27
Family sizes

m5ad.8xlarge

m5ad.8xlarge is AWS's general-purpose EC2 size at 32 vCPU and 128 GiB. In US East (N. Virginia), the closest Rackspace Spot server is gp.vs1.2xlarge at 16 vCPU and 64 GiB, so you will need 2 of them to get a total of 32 vCPU and 128 GiB.

Even with 2 servers, Rackspace Spot's on-demand price is about 63% below AWS on-demand and its Spot market price is about 87% 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 m5ad.8xlarge gives you 32 vCPU and 128 GiB in a single machine. The largest comparable Rackspace Spot server, gp.vs1.2xlarge, is 16 vCPU and 64 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 128 GiB in one process, it does not.

No local disk

The AWS m5ad.8xlarge comes with 2 × 600 GB NVMe 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$1.648$0.616$1.038$0.712$0.608$0.082
$1.040 (63%)
$0.534 (87%)
US Central, Chicagono AWS regionn/an/an/a$0.672$0.022n/an/a
US Central, Dallasno AWS regionn/an/an/a$0.646$0.142n/an/a
Hong Kongnot sold heren/an/an/a$0.678$0.022n/an/a
Sydney, Australia$2.080$0.826$1.310$0.899$0.638$0.022
$1.442 (69%)
$0.804 (97%)
London, UK$1.920$0.669$1.210$0.829$0.578$0.262
$1.342 (70%)
$0.407 (61%)
US West, San Jose$1.952$0.759$1.230$0.843$0.700$0.302
$1.252 (64%)
$0.458 (60%)
US Central, Dallas 2no AWS regionn/an/an/a$0.680$0.002n/an/a
US East, N. Virginia 2$1.648$0.616$1.038$0.712$0.700$0.382
$0.948 (58%)
$0.234 (38%)

Prices updated 17 Nov 2026.

When to use it

Good for
  • ●Queue workers and scheduled jobs
  • ●Web and application servers with mixed CPU and memory demand
  • ●Microservices and container fleets
  • ●Workloads that fit inside 128 GiB of RAM
  • ●Jobs that want 2 × 600 GB of local NVMe scratch space
  • ●Network-heavy services (AWS rates this size at Up to 10 Gigabit)
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m6i.8xlarge is the newer generation at this size.
  • ●The working set needs more than 128 GiB of RAM
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
  • ●More than 4.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.
m5ad.8xlarge is $1,203/mo on AWS on-demand and $444/mo on Rackspace Spot on-demand for 2 servers, 63% less. At the Spot market price, the same capacity is $60/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 m5ad.8xlarge cost?

The AWS m5ad.8xlarge costs $1.65/hr on-demand in US East (N. Virginia), about $1,203/mo running 24/7, or $0.616/hr at the AWS Spot price. On Rackspace Spot, 2 × gp.vs1.2xlarge is $0.608/hr on-demand, or $0.082/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 m5ad.8xlarge per month?

At 730 hours a month, m5ad.8xlarge in US East (N. Virginia) is $1,203/mo on AWS on-demand, or $450/mo at the AWS Spot price. The same capacity on Rackspace Spot (2 × gp.vs1.2xlarge) is $444/mo on-demand, or $60/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 m5ad.8xlarge?

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

Does the Rackspace Spot equivalent include local NVMe storage?

No. m5ad.8xlarge ships 2 × 600 GB of local NVMe SSD, rated 466,666 read IOPS. 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 m5ad.8xlarge still worth using?

For workloads already running on it, yes: it works and it is priced accordingly. For anything new, m6i.8xlarge is the current answer and measures roughly 42% more CoreMark throughput at the same vCPU count. 4 newer generations of the m family have shipped since (m6i, m7i, m8i and m9g), which is the signal that matters for infrastructure you expect to keep running.

What is the difference between m5ad and m6i?

m6i is the newer generation. It runs on Intel Xeon 8375C (Ice Lake) against m5ad's AMD EPYC 7571. On the CoreMark figures in this dataset, m6i.8xlarge scores 550,372 per second against m5ad.8xlarge's 386,551. On-demand in US East (N. Virginia) the newer size is 7% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.