AWS EC2 Instances›Compute Optimized›c8ib›c8ib.16xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinec8ib.16xlarge4 × ch.vs1.2xlarge
vCPU6464
Memory128 GiB128 GiB
Local diskNoneNone
On-demand / hr$4.355$1.044
Spot / hr$1.393$0.164
Prices in US East, N. Virginia

Compute

vCPUs64
Memory128 GiB
Mem / vCPU2.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPSN/A
CoreMark / secN/A

Storage

TypeEBS only
Bandwidth50,000 Mbps
Throughput6250 MB/s
IOPS240,000
Base Bandwidth50,000 Mbps
Base Throughput6250 MB/s
Base IOPS240,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance66.66 Gigabit
Max ENIs16
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingNo
Branch Interface0
IPs / ENI64
Baseline Bandwidth66.666 Gbps

NUMA Architecture

Uses NUMANo
Node CountN/A
Max DistanceN/A
Cores / NodeN/A
Threads / NodeN/A
Memory / NodeN/A
L3 Cache / NodeN/A
L3 Cache SharedN/A

AWS Metadata

Instance typec8ib.16xlarge
Full nameC8IB 16xlarge Extra Large
FamilyCompute optimized
Variantc8ib
GenerationCurrent
Bare MetalNo
EMR supportNo
DedicatedSupported
Introduced2026-04-16
Family sizes

c8ib.16xlarge

c8ib.16xlarge is AWS's compute-optimized EC2 size at 64 vCPU and 128 GiB. In US East (N. Virginia), the closest Rackspace Spot server is ch.vs1.2xlarge at 16 vCPU and 32 GiB, so you will need 4 of them to get a total of 64 vCPU and 128 GiB.

Even with 4 servers, Rackspace Spot's on-demand price is about 76% below AWS on-demand and its Spot market price is about 88% below AWS Spot. Rackspace Spot offers managed Kubernetes, so you can run them together in one cluster.

Server comparison caveats
Scale-out match

The AWS c8ib.16xlarge gives you 64 vCPU and 128 GiB in a single machine. The largest comparable Rackspace Spot server, ch.vs1.2xlarge, is 16 vCPU and 32 GiB, so the equivalent here is 4 servers rather than one.

This setup works best for Kubernetes workloads, or for workloads that already sit behind a load balancer, a queue or a scheduler, because they spread across the 4 servers without changes. If it needs all 64 cores and 128 GiB in one process, it does not.

Pricing by region

1 hr

Regions are Rackspace Spot locations.

RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace on-demandRackspace SpotOn-demand price savingsSpot price savings
US East, N. Virginia$4.355$1.393not offerednot offered$1.044$0.164
$3.311 (76%)
$1.230 (88%)
US Central, Chicagono AWS regionn/an/an/a$1.108$0.044n/an/a
US Central, Dallasno AWS regionn/an/an/a$1.100$0.524n/an/a
Hong Kongnot sold heren/an/an/a$1.080$0.044n/an/a
Sydney, Australianot sold heren/an/an/a$1.168$0.144n/an/a
London, UKnot sold heren/an/an/a$1.036$0.164n/an/a
US West, San Josenot sold heren/an/an/a$1.040$0.008n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$1.040$0.488n/an/a
US East, N. Virginia 2$4.355$1.393not offerednot offered$1.040$0.488
$3.315 (76%)
$0.905 (65%)

Prices updated 17 Nov 2026.

When to use it

Good for
  • ●Scientific modelling and simulation
  • ●Ad serving and real-time bidding
  • ●Game servers and matchmaking
  • ●Workloads that fit inside 128 GiB of RAM
  • ●Parallel work that can occupy 64 vCPU
  • ●Network-heavy services (AWS rates this size at 66.66 Gigabit)
  • ●Anything that shards cleanly across 4 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 128 GiB of RAM
  • ●GPU or FPGA acceleration is needed
  • ●Memory-hungry applications. A memory-optimized family gives more RAM per dollar.
  • ●More than 2.00 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 64 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
c8ib.16xlarge is $3,179/mo on AWS on-demand and $762/mo on Rackspace Spot on-demand for 4 servers, 76% less. At the Spot market price, the same capacity is $120/mo.
  • Rackspace 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

How much does c8ib.16xlarge cost?

The AWS c8ib.16xlarge costs $4.35/hr on-demand in US East (N. Virginia), about $3,179/mo running 24/7, or $1.39/hr at the AWS Spot price. On Rackspace Spot, 4 × ch.vs1.2xlarge is $1.04/hr on-demand, or $0.164/hr at the Spot price. Rackspace Spot also sells in Chicago and Dallas, where AWS operates no region at all, so those rows have no AWS price to compare against.

How much is c8ib.16xlarge per month?

At 730 hours a month, c8ib.16xlarge in US East (N. Virginia) is $3,179/mo on AWS on-demand, or $1,017/mo at the AWS Spot price. The same capacity on Rackspace Spot (4 × ch.vs1.2xlarge) is $762/mo on-demand, or $120/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

How many Rackspace Spot nodes replace one c8ib.16xlarge?

4. The ch.vs1.2xlarge server is 16 vCPU and 32 GiB, and Rackspace Spot's whole VM catalog tops out at 16 vCPU, so covering 64 vCPU and 128 GiB takes 4 of them: 64 vCPU and 128 GiB in total. Per-region fleet sizes differ and are shown in the table.

What is the difference between c8ib and c9g?

c9g is the newer generation. It runs on AWS Graviton5 Processor against c8ib's Intel Xeon Scalable (Granite Rapids). On-demand in US East (N. Virginia) the newer size is 36% cheaper. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.

What is a cheaper alternative to c8ib.16xlarge?

Rackspace Spot 4 × ch.vs1.2xlarge (64 vCPU, 128 GiB) is $762/mo on-demand or $120/mo at the Spot price, against $3,179/mo on-demand or $1,017/mo at the Spot price for c8ib.16xlarge on AWS in US East (N. Virginia). The trade is real: Rackspace Spot capacity is priced by demand and can be reclaimed when demand rises, and workloads have to be containerized.