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

Compared with Rackspace Spot

AWSRackspace Spot
Machinem6idn.8xlarge2 × gp.vs2.2xlarge
vCPU3232
Memory128 GiB128 GiB
Local disk1 × 1,900 GB NVMe SSDNone
On-demand / hr$2.935$0.700
Spot / hr$1.744$0.302
Prices in US West, San Jose

Compute

vCPUs32
Memory128 GiB
Mem / vCPU4.00 GiB
ProcessorXeon 8375C
Clock speed3.5 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS148
CoreMark / sec560,200

Storage

Type1 × 1,900 GB NVMe SSD
Bandwidth25,000 Mbps
Throughput3125 MB/s
IOPS100,000
Base Bandwidth25,000 Mbps
Base Throughput3125 MB/s
Base IOPS100,000
Devices1
NVMe DriveYes
SSDYes
Swap PartitionNo
Local Read IOPS536,666
Local Write IOPS268,334

Networking

Performance50 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface84
IPs / ENI30
Baseline Bandwidth50 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 typem6idn.8xlarge
Full nameM6IDN Eight Extra Large
FamilyGeneral purpose
Variantm6idn
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2022-11-28
Family sizes

m6idn.8xlarge

m6idn.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 76% 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 m6idn.8xlarge gives you 32 vCPU and 128 GiB in a single machine. The largest comparable Rackspace Spot server, gp.vs2.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 m6idn.8xlarge comes with 1 × 1,900 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$2.546$1.115$1.604$0.990$0.608$0.082
$1.938 (76%)
$1.034 (93%)
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.162n/an/a
Hong Kongnot sold heren/an/an/a$0.678$0.022n/an/a
Sydney, Australia$3.220$1.175$2.029$1.391$0.638$0.082
$2.582 (80%)
$1.093 (93%)
London, UK$2.896$0.679$1.824$1.116$0.578$0.262
$2.318 (80%)
$0.417 (61%)
US West, San Jose$2.935$1.744$1.849$1.131$0.700$0.302
$2.235 (76%)
$1.442 (83%)
US Central, Dallas 2no AWS regionn/an/an/a$0.680$0.002n/an/a
US East, N. Virginia 2$2.546$1.115$1.604$0.990$0.700$0.382
$1.846 (73%)
$0.734 (66%)

Prices updated 18 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 1 × 1,900 GB of local NVMe scratch space
  • ●Network-heavy services (AWS rates this size at 50 Gigabit)
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m7i.8xlarge is the newer generation at this size.
  • ●The working set needs more than 128 GiB of RAM
  • ●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.
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
m6idn.8xlarge is $1,859/mo on AWS on-demand and $444/mo on Rackspace Spot on-demand for 2 servers, 76% 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 m6idn.8xlarge cost?

The AWS m6idn.8xlarge costs $2.55/hr on-demand in US East (N. Virginia), about $1,859/mo running 24/7, or $1.12/hr at the AWS Spot price. On Rackspace Spot, 2 × gp.vs2.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 m6idn.8xlarge per month?

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

2. The gp.vs2.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. m6idn.8xlarge ships 1 × 1,900 GB of local NVMe SSD, rated 536,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 m6idn.8xlarge still worth using?

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

What is the difference between m6idn and m7i?

m7i is the newer generation. It runs on Intel Xeon Scalable (Sapphire Rapids) against m6idn's Intel Xeon 8375C (Ice Lake). On the CoreMark figures in this dataset, m7i.8xlarge scores 699,530 per second against m6idn.8xlarge's 560,200. On-demand in US East (N. Virginia) the newer size is 37% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.