Instances›AWS EC2›c9g›c9g.8xlarge
Compute
vCPUs32
Memory64 GiB
Mem / vCPU2.00 GiB
ProcessorGraviton5 Processor
Clock speed3.3 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth12,000 Mbps
Throughput1500 MB/s
IOPS48,000
Networking
Performance17 Gigabit
Max ENIs10
IPv6Yes
GPUNone
Family sizes
c9g.medium1 vCPU · 2 GiB
c9g.large2 vCPU · 4 GiB
c9g.xlarge4 vCPU · 8 GiB
c9g.2xlarge8 vCPU · 16 GiB
c9g.4xlarge16 vCPU · 32 GiB
c9g.8xlarge32 vCPU · 64 GiB
c9g.12xlarge48 vCPU · 96 GiB
c9g.16xlarge64 vCPU · 128 GiB
c9g.24xlarge96 vCPU · 192 GiB
c9g.48xlarge192 vCPU · 384 GiB
c9g.metal-48xl192 vCPU · 384 GiB
c9g.8xlarge

The c9g.8xlarge pairs 32 vCPU with 64 GiB of RAM, the 2.00 GiB-per-vCPU ratio that marks a compute-optimized instance. In the name, "c" stands for compute, "9" is the generation, "g" marks AWS Graviton (ARM) processors and "8xlarge" is the size within the c9g family. It runs on AWS Graviton5 Processor at 3.3 GHz, and AWS introduced it in June 2026. c9g is the current generation of the c family, so there is no newer AWS size to migrate to. Spot's node ladder tops out below this size, so c9g.8xlarge becomes 2 × ch.vs1.2xlarge (32 vCPU, 64 GiB combined), about 94% 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

c9g.8xlarge gives you 32 vCPU and 64 GiB in a single machine. The largest comparable Spot node, ch.vs1.2xlarge, is 16 vCPU and 32 GiB, so the equivalent here is 2 nodes rather than one.

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

x86_64 onlyc9g.8xlarge 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.391$0.459$0.082
$1.309 savings
US Central, Chicagono AWS region$0.022
US Central, Dallasno AWS region$0.222
Hong Kong$0.082
Sydney, Australia$0.082
London, UK$0.262
US West, San Jose$0.004
US Central, Dallas 2no AWS region$0.244
US East, N. Virginia 2$1.391$0.459$0.324
$1.067 savings
When to use it
Good for
  • ●Video encoding and transcoding
  • ●High-traffic web and API serving
  • ●Scientific modelling and simulation
  • ●Workloads that fit inside 64 GiB of RAM
  • ●Parallel work that can occupy 32 vCPU
  • ●Network-heavy services — AWS rates this size at 17 Gigabit
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 64 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●More than 2.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 32 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
Stop overpaying AWS. This compute costs $1,015/mo on AWS vs $60/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