Instances›AWS EC2›x8g›x8g.12xlarge
Compute
vCPUs48
Memory768 GiB
Mem / vCPU16.00 GiB
ProcessorGraviton4 Processor
Clock speed2.7 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth15,000 Mbps
Throughput1875 MB/s
IOPS60,000
Networking
Performance22.5 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
x8g.medium1 vCPU · 16 GiB
x8g.large2 vCPU · 32 GiB
x8g.xlarge4 vCPU · 64 GiB
x8g.2xlarge8 vCPU · 128 GiB
x8g.4xlarge16 vCPU · 256 GiB
x8g.8xlarge32 vCPU · 512 GiB
x8g.12xlarge48 vCPU · 768 GiB
x8g.16xlarge64 vCPU · 1024 GiB
x8g.24xlarge96 vCPU · 1536 GiB
x8g.metal-24xl96 vCPU · 1536 GiB
x8g.48xlarge192 vCPU · 3072 GiB
x8g.metal-48xl192 vCPU · 3072 GiB
x8g.12xlarge

x8g.12xlarge is AWS's memory-optimized EC2 size at 48 vCPU and 768 GiB. In the name, "x" is the extra-memory line, "8" is the generation, "g" marks AWS Graviton (ARM) processors and "12xlarge" is the size within the x8g family. It runs on AWS Graviton4 Processor at 2.7 GHz, and AWS introduced it in September 2024. x8g is the current generation of the x family, so there is no newer AWS size to migrate to. The closest Spot shape is mh.vs1.2xlarge at 16 vCPU, so this instance maps to 6 of them — 96 vCPU and 768 GiB across the fleet, $4.69/hr on AWS in US East (N. Virginia), from $0.126/hr on Rackspace Spot. 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

x8g.12xlarge gives you 48 vCPU and 768 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 6 nodes rather than one.

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

x86_64 onlyx8g.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$4.690$2.289$2.890$1.602$0.126
$4.564 savings
US Central, Chicagono AWS region$0.126
US Central, Dallasno AWS region$0.786
Hong Kong$0.126
Sydney, Australia$5.628$0.927$3.468$1.922$0.126
$5.502 savings
London, UK$0.786
US West, San Jose$0.011
US Central, Dallas 2no AWS region$1.331
When to use it
Good for
  • ●Large JVM heaps and application servers that hold state
  • ●OLAP and business intelligence query engines
  • ●Real-time analytics over hot datasets
  • ●Workloads that fit inside 768 GiB of RAM
  • ●Parallel work that can occupy 48 vCPU
  • ●Network-heavy services — AWS rates this size at 22.5 Gigabit
  • ●Anything that shards cleanly across 6 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
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 16.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
Stop overpaying AWS. This compute costs $3,423/mo on AWS vs $92/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