Instances›AWS EC2›m9g›m9g.metal-48xl
Compute
vCPUs192
Memory768 GiB
Mem / vCPU4.00 GiB
ProcessorGraviton5 Processor
Clock speed3.3 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth72,000 Mbps
Throughput9000 MB/s
IOPS288,000
Networking
Performance100 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Family sizes
m9g.medium1 vCPU · 4 GiB
m9g.large2 vCPU · 8 GiB
m9g.xlarge4 vCPU · 16 GiB
m9g.2xlarge8 vCPU · 32 GiB
m9g.4xlarge16 vCPU · 64 GiB
m9g.8xlarge32 vCPU · 128 GiB
m9g.12xlarge48 vCPU · 192 GiB
m9g.16xlarge64 vCPU · 256 GiB
m9g.24xlarge96 vCPU · 384 GiB
m9g.48xlarge192 vCPU · 768 GiB
m9g.metal-48xl192 vCPU · 768 GiB
m9g.metal-48xl

The m9g.metal-48xl pairs 192 vCPU with 768 GiB of RAM, the 4.00 GiB-per-vCPU ratio that marks a general-purpose instance. In the name, "m" is the general-purpose line, "9" is the generation, "g" marks AWS Graviton (ARM) processors and "metal-48xl" is the size within the m9g family. It runs on AWS Graviton5 Processor at 3.3 GHz, and AWS introduced it in June 2026. m9g is the current generation of the m family, so there is no newer AWS size to migrate to. Spot's node ladder tops out below this size, so m9g.metal-48xl becomes 12 × gp.vs2.2xlarge (192 vCPU, 768 GiB combined), about 95% 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

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

Spot runs as managed Kubernetes, so a 12-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 192 cores and 768 GiB in one process, it does not.

x86_64 onlym9g.metal-48xl 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$9.393$1.960$0.492
$8.901 savings
US Central, Chicagono AWS region$0.492
US Central, Dallasno AWS region$0.612
Hong Kong$0.132
Sydney, Australia$11.741$1.174$1.932
$9.809 savings
London, UK$2.652
US West, San Jose$1.812
US Central, Dallas 2no AWS region$0.012
US East, N. Virginia 2$9.393$1.960$1.812
$7.581 savings
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 768 GiB of RAM
  • ●Parallel work that can occupy 192 vCPU
  • ●Network-heavy services — AWS rates this size at 100 Gigabit
  • ●Anything that shards cleanly across 12 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 768 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●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 — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 192 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
m9g.metal-48xl runs $6,857/mo on AWS on-demand. The 12-node equivalent on Rackspace Spot: $359/mo.
  • 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