Instances›AWS EC2›r6id›r6id.16xlarge
Compute
vCPUs64
Memory512 GiB
Mem / vCPU8.00 GiB
ProcessorXeon 8375C
Clock speed3.5 GHz
Architecturex86_64
Storage
Type2 × 1,900 GB NVMe SSD
Bandwidth20,000 Mbps
Throughput2500 MB/s
IOPS80,000
Networking
Performance25 Gigabit
Max ENIs15
IPv6Yes
GPUNone
Family sizes
r6id.large2 vCPU · 16 GiB
r6id.xlarge4 vCPU · 32 GiB
r6id.2xlarge8 vCPU · 64 GiB
r6id.4xlarge16 vCPU · 128 GiB
r6id.8xlarge32 vCPU · 256 GiB
r6id.12xlarge48 vCPU · 384 GiB
r6id.16xlarge64 vCPU · 512 GiB
r6id.24xlarge96 vCPU · 768 GiB
r6id.32xlarge128 vCPU · 1024 GiB
r6id.metal128 vCPU · 1024 GiB
r6id.16xlarge

The r6id.16xlarge pairs 64 vCPU with 512 GiB of RAM, the 8.00 GiB-per-vCPU ratio that marks a memory-optimized instance. In the name, "r" stands for RAM, "6" is the generation, "id" marks Intel processors and local NVMe storage and "16xlarge" is the size within the r6id family. It runs on Intel Xeon 8375C (Ice Lake) at 3.5 GHz, and AWS introduced it in June 2022. AWS has since shipped r7i, r8id and r9g; r7i.16xlarge is the direct replacement at this size. Spot's node ladder tops out below this size, so r6id.16xlarge becomes 4 × mh.vs1.2xlarge (64 vCPU, 512 GiB combined), $4.84/hr on AWS in US East (N. Virginia), from $0.084/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

r6id.16xlarge gives you 64 vCPU and 512 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 4 nodes rather than one.

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

No local diskr6id.16xlarge comes with 2 × 1,900 GB NVMe SSD attached to the machine. Spot nodes use network storage only, so that disk doesn't come with it. If you were using it as fast scratch space, you'd move to a persistent volume or object storage, which are slower to read.
Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$4.838$3.417$3.041$2.091$0.084
$4.754 savings
US Central, Chicagono AWS region$0.084
US Central, Dallasno AWS region$0.524
Hong Kong$0.084
Sydney, Australia$5.568$1.925$3.508$2.405$0.084
$5.484 savings
London, UK$5.678$0.568$3.577$2.453$0.524
$5.154 savings
US West, San Jose$0.008
US Central, Dallas 2no AWS region$0.968
When to use it
Good for
  • ●Database instances that keep the working set in RAM
  • ●Graph and search workloads with large indexes
  • ●In-memory caches such as Redis and Memcached
  • ●Workloads that fit inside 512 GiB of RAM
  • ●Jobs that want 2 × 1,900 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 25 Gigabit
  • ●Anything that shards cleanly across 4 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. r7i.16xlarge is the newer generation at this size.
  • ●The working set needs more than 512 GiB of RAM
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 8.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 64 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
Stop overpaying AWS. This compute costs $3,532/mo on AWS vs $61/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