Instances›AWS EC2›m6g›m6g.12xlarge
Compute
vCPUs48
Memory192 GiB
Mem / vCPU4.00 GiB
ProcessorGraviton2 Processor
Clock speed2.5 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth14,250 Mbps
Throughput1781.25 MB/s
IOPS50,000
Networking
Performance20 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
m6g.medium1 vCPU · 4 GiB
m6g.large2 vCPU · 8 GiB
m6g.xlarge4 vCPU · 16 GiB
m6g.2xlarge8 vCPU · 32 GiB
m6g.4xlarge16 vCPU · 64 GiB
m6g.8xlarge32 vCPU · 128 GiB
m6g.12xlarge48 vCPU · 192 GiB
m6g.16xlarge64 vCPU · 256 GiB
m6g.metal64 vCPU · 256 GiB
m6g.12xlarge

m6g.12xlarge is AWS's general-purpose EC2 size at 48 vCPU and 192 GiB. In the name, "m" is the general-purpose line, "6" is the generation, "g" marks AWS Graviton (ARM) processors and "12xlarge" is the size within the m6g family. It runs on AWS Graviton2 Processor at 2.5 GHz, and AWS introduced it in May 2020. AWS has since shipped m7g, m8g and m9g; m7g.12xlarge is the direct replacement at this size, scoring 1,244,733 CoreMark/s against this instance's 932,039 — roughly 34% more throughput for the same vCPU count. The closest Spot shape is gp.vs2.2xlarge at 16 vCPU, so this instance maps to 3 of them — 48 vCPU and 192 GiB across the fleet, about 93% below the US East (N. Virginia) on-demand rate. Spot delivers compute as managed Kubernetes, so a node pool of that size is the native shape of the answer rather than a workaround — provided the workload scales horizontally.

Match qualityScale-out match

m6g.12xlarge gives you 48 vCPU and 192 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 3 nodes rather than one.

Spot runs as managed Kubernetes, so a 3-node pool is the normal way to run things rather than a workaround. If your workload already sits behind a load balancer, a queue or a scheduler, it spreads across them without changes. If it needs all 48 cores and 192 GiB in one process, it does not.

x86_64 onlym6g.12xlarge is Graviton (arm64) and Rackspace Spot has no arm64 nodes, so you'd be moving to x86. You'll need x86 builds of your images, and per-core speed differs between the chips — worth testing before you decide how many nodes to run.
Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$1.848$0.496$1.159$0.803$0.123
$1.725 savings
US Central, Chicagono AWS region$0.123
US Central, Dallasno AWS region$0.153
Hong Kong$2.544$1.587$1.089$0.033
$2.511 savings
Sydney, Australia$2.304$0.729$1.452$0.995$0.483
$1.821 savings
London, UK$2.131$0.542$1.343$0.921$0.663
$1.468 savings
US West, San Jose$2.150$0.642$1.355$0.929$0.453
$1.697 savings
US Central, Dallas 2no AWS region$0.003
US East, N. Virginia 2$1.848$0.496$1.159$0.803$0.453
$1.395 savings
When to use it
Good for
  • ●Web and application servers with mixed CPU and memory demand
  • ●Microservices and container fleets
  • ●Development, staging and CI environments
  • ●Workloads that fit inside 192 GiB of RAM
  • ●Parallel work that can occupy 48 vCPU
  • ●Network-heavy services — AWS rates this size at 20 Gigabit
  • ●Anything that shards cleanly across 3 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m7g.12xlarge is the newer generation at this size.
  • ●The working set needs more than 192 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
Stop overpaying AWS. This compute costs $1,349/mo on AWS vs $90/mo on Rackspace Spot.
  • 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