Instances›AWS EC2›c6g›c6g.8xlarge
Compute
vCPUs32
Memory64 GiB
Mem / vCPU2.00 GiB
ProcessorGraviton2 Processor
Clock speed2.5 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth9,500 Mbps
Throughput1187.5 MB/s
IOPS40,000
Networking
Performance12 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
c6g.medium1 vCPU · 2 GiB
c6g.large2 vCPU · 4 GiB
c6g.xlarge4 vCPU · 8 GiB
c6g.2xlarge8 vCPU · 16 GiB
c6g.4xlarge16 vCPU · 32 GiB
c6g.8xlarge32 vCPU · 64 GiB
c6g.12xlarge48 vCPU · 96 GiB
c6g.16xlarge64 vCPU · 128 GiB
c6g.metal64 vCPU · 128 GiB
c6g.8xlarge

c6g.8xlarge is AWS's compute-optimized EC2 size at 32 vCPU and 64 GiB. In the name, "c" stands for compute, "6" is the generation, "g" marks AWS Graviton (ARM) processors and "8xlarge" is the size within the c6g family. It runs on AWS Graviton2 Processor at 2.5 GHz, and AWS introduced it in June 2020. AWS has since shipped c7g, c8g and c9g; c7g.8xlarge is the direct replacement at this size, scoring 807,877 CoreMark/s against this instance's 647,162 — roughly 25% more throughput for the same vCPU count. The closest Spot shape is ch.vs1.2xlarge at 16 vCPU, so this instance maps to 2 of them — 32 vCPU and 64 GiB across the fleet, about 92% 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

c6g.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 onlyc6g.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.088$0.337$0.685$0.470$0.082
$1.006 savings
US Central, Chicagono AWS region$0.022
US Central, Dallasno AWS region$0.222
Hong Kong$1.376$0.874$0.605$0.082
$1.294 savings
Sydney, Australia$1.421$0.440$0.895$0.614$0.082
$1.339 savings
London, UK$1.293$0.415$0.815$0.558$0.262
$1.031 savings
US West, San Jose$1.357$0.455$0.855$0.586$0.004
$1.353 savings
US Central, Dallas 2no AWS region$0.244
US East, N. Virginia 2$1.088$0.337$0.685$0.470$0.324
$0.764 savings
When to use it
Good for
  • ●Batch processing and CI/CD runners
  • ●Video encoding and transcoding
  • ●High-traffic web and API serving
  • ●Workloads that fit inside 64 GiB of RAM
  • ●Parallel work that can occupy 32 vCPU
  • ●Network-heavy services — AWS rates this size at 12 Gigabit
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. c7g.8xlarge is the newer generation at this size.
  • ●The working set needs more than 64 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●Memory-hungry applications. A memory-optimized family gives more RAM per dollar.
  • ●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.
c6g.8xlarge runs $794/mo on AWS on-demand. The 2-node equivalent on Rackspace Spot: $60/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