AWS EC2 Instances›General Purpose›m6id›m6id.32xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinem6id.32xlarge8 × gp.vs2.2xlarge
vCPU128128
Memory512 GiB512 GiB
Local disk4 × 1,900 GB NVMe SSDNone
On-demand / hr$8.938$2.800
Spot / hr$2.465$1.208
Prices in US West, San Jose

Compute

vCPUs128
Memory512 GiB
Mem / vCPU4.00 GiB
ProcessorXeon 8375C
Clock speed3.5 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS213
CoreMark / sec2,204,901

Storage

Type4 × 1,900 GB NVMe SSD
Bandwidth40,000 Mbps
Throughput5000 MB/s
IOPS160,000
Base Bandwidth40,000 Mbps
Base Throughput5000 MB/s
Base IOPS160,000
Devices4
NVMe DriveYes
SSDYes
Swap PartitionNo
Local Read IOPS2,146,664
Local Write IOPS1,073,336

Networking

Performance50 Gigabit
Max ENIs15
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface107
IPs / ENI50
Baseline Bandwidth50 Gbps

NUMA Architecture

Uses NUMAYes
Node Count2
Max Distance20
Cores / Node32
Threads / Node64
Memory / Node253,907.5 MB
L3 Cache / Node54 MB
L3 Cache SharedYes

AWS Metadata

Instance typem6id.32xlarge
Full nameM6ID 32xlarge
FamilyGeneral purpose
Variantm6id
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2022-05-26
Family sizes

m6id.32xlarge

AWS's m6id.32xlarge is a general-purpose instance with 128 vCPU and 512 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 8 of them to get a total of 128 vCPU and 512 GiB.

Even with 8 servers, Rackspace Spot's on-demand price is about 68% below AWS on-demand and its Spot market price is about 86% 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 m6id.32xlarge gives you 128 vCPU and 512 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 8 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 8 servers without changes. If it needs all 128 cores and 512 GiB in one process, it does not.

No local disk

The AWS m6id.32xlarge comes with 4 × 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$7.594$2.285$4.784$3.280$2.432$0.328
$5.162 (68%)
$1.957 (86%)
US Central, Chicagono AWS regionn/an/an/a$2.688$0.088n/an/a
US Central, Dallasno AWS regionn/an/an/a$2.584$0.648n/an/a
Hong Kongnot sold heren/an/an/a$2.712$0.088n/an/a
Sydney, Australia$9.542$2.233$6.012$4.122$2.552$0.328
$6.990 (73%)
$1.905 (85%)
London, UK$8.803$2.104$5.546$3.803$2.312$1.048
$6.491 (74%)
$1.056 (50%)
US West, San Jose$8.938$2.465$5.631$3.861$2.800$1.208
$6.138 (69%)
$1.257 (51%)
US Central, Dallas 2no AWS regionn/an/an/a$2.720$0.008n/an/a
US East, N. Virginia 2$7.594$2.285$4.784$3.280$2.800$1.528
$4.794 (63%)
$0.757 (33%)

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 512 GiB of RAM
  • ●Jobs that want 4 × 1,900 GB of local NVMe scratch space
  • ●Network-heavy services (AWS rates this size at 50 Gigabit)
  • ●Anything that shards cleanly across 8 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m7a.32xlarge is the newer generation at this size.
  • ●The working set needs more than 512 GiB of RAM
  • ●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 128 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
m6id.32xlarge is $5,543/mo on AWS on-demand and $1,775/mo on Rackspace Spot on-demand for 8 servers, 68% less. At the Spot market price, the same capacity is $239/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 m6id.32xlarge cost?

The AWS m6id.32xlarge costs $7.59/hr on-demand in US East (N. Virginia), about $5,543/mo running 24/7, or $2.29/hr at the AWS Spot price. On Rackspace Spot, 8 × gp.vs2.2xlarge is $2.43/hr on-demand, or $0.328/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 m6id.32xlarge per month?

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

8. 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 128 vCPU and 512 GiB takes 8 of them: 128 vCPU and 512 GiB in total. Per-region fleet sizes differ and are shown in the table.

Does the Rackspace Spot equivalent include local NVMe storage?

No. m6id.32xlarge ships 4 × 1,900 GB of local NVMe SSD, rated 2,146,664 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 m6id.32xlarge still worth using?

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

What is the difference between m6id and m7a?

m7a is the newer generation. It runs on AMD EPYC 9R14 Processor against m6id's Intel Xeon 8375C (Ice Lake). On the CoreMark figures in this dataset, m7a.32xlarge scores 4,116,638 per second against m6id.32xlarge's 2,204,901. On-demand in US East (N. Virginia) the newer size is 2% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.