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

Compared with Rackspace Spot

AWSRackspace Spot
Machinem6id.12xlarge3 × gp.vs2.2xlarge
vCPU4848
Memory192 GiB192 GiB
Local disk2 × 1,425 GB NVMe SSDNone
On-demand / hr$3.352$1.050
Spot / hr$1.011$0.453
Prices in US West, San Jose

Compute

vCPUs48
Memory192 GiB
Mem / vCPU4.00 GiB
ProcessorXeon 8375C
Clock speed3.5 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS219
CoreMark / sec820,443

Storage

Type2 × 1,425 GB NVMe SSD
Bandwidth15,000 Mbps
Throughput1875 MB/s
IOPS60,000
Base Bandwidth15,000 Mbps
Base Throughput1875 MB/s
Base IOPS60,000
Devices2
NVMe DriveYes
SSDYes
Swap PartitionNo
Local Read IOPS804,998
Local Write IOPS402,500

Networking

Performance18.75 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface114
IPs / ENI30
Baseline Bandwidth18.75 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 typem6id.12xlarge
Full nameM6ID 12xlarge Extra Large
FamilyGeneral purpose
Variantm6id
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2022-05-26
Family sizes

m6id.12xlarge

AWS's m6id.12xlarge is a general-purpose instance with 48 vCPU and 192 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 3 of them to get a total of 48 vCPU and 192 GiB.

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

No local disk

The AWS m6id.12xlarge comes with 2 × 1,425 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.848$0.761$1.794$1.230$0.912$0.123
$1.936 (68%)
$0.638 (84%)
US Central, Chicagono AWS regionn/an/an/a$1.008$0.033n/an/a
US Central, Dallasno AWS regionn/an/an/a$0.969$0.243n/an/a
Hong Kongnot sold heren/an/an/a$1.017$0.033n/an/a
Sydney, Australia$3.578$1.295$2.254$1.546$0.957$0.123
$2.621 (73%)
$1.172 (91%)
London, UK$3.301$0.705$2.080$1.426$0.867$0.393
$2.434 (74%)
$0.312 (44%)
US West, San Jose$3.352$1.011$2.111$1.448$1.050$0.453
$2.302 (69%)
$0.558 (55%)
US Central, Dallas 2no AWS regionn/an/an/a$1.020$0.003n/an/a
US East, N. Virginia 2$2.848$0.761$1.794$1.230$1.050$0.573
$1.798 (63%)
$0.188 (25%)

Prices updated 18 Nov 2026.

When to use it

Good for
  • ●Microservices and container fleets
  • ●Development, staging and CI environments
  • ●Small to mid-size relational databases
  • ●Workloads that fit inside 192 GiB of RAM
  • ●Jobs that want 2 × 1,425 GB of local NVMe scratch space
  • ●Network-heavy services (AWS rates this size at 18.75 Gigabit)
  • ●Anything that shards cleanly across 3 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m7i.12xlarge is the newer generation at this size.
  • ●The working set needs more than 192 GiB of RAM
  • ●The work is single-threaded. Most of these 48 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.
  • ●More than 4.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
m6id.12xlarge is $2,079/mo on AWS on-demand and $666/mo on Rackspace Spot on-demand for 3 servers, 68% less. At the Spot market price, the same capacity is $90/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.12xlarge cost?

The AWS m6id.12xlarge costs $2.85/hr on-demand in US East (N. Virginia), about $2,079/mo running 24/7, or $0.761/hr at the AWS Spot price. On Rackspace Spot, 3 × gp.vs2.2xlarge is $0.912/hr on-demand, or $0.123/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.12xlarge per month?

At 730 hours a month, m6id.12xlarge in US East (N. Virginia) is $2,079/mo on AWS on-demand, or $556/mo at the AWS Spot price. The same capacity on Rackspace Spot (3 × gp.vs2.2xlarge) is $666/mo on-demand, or $90/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.12xlarge?

3. 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 48 vCPU and 192 GiB takes 3 of them: 48 vCPU and 192 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.12xlarge ships 2 × 1,425 GB of local NVMe SSD, rated 804,998 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.12xlarge still worth using?

For workloads already running on it, yes: it works and it is priced accordingly. For anything new, m7i.12xlarge is the current answer and measures roughly 30% 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 m7i?

m7i is the newer generation. It runs on Intel Xeon Scalable (Sapphire Rapids) against m6id's Intel Xeon 8375C (Ice Lake). On the CoreMark figures in this dataset, m7i.12xlarge scores 1,068,012 per second against m6id.12xlarge's 820,443. On-demand in US East (N. Virginia) the newer size is 15% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.