AWS EC2 Instances›Memory Optimized›u7in-24tb›u7in-24tb.224xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machineu7in-24tb.224xlarge175 × mh.vs1.2xlarge
vCPU8962800
Memory24576 GiB22400 GiB
Local diskNoneNone
On-demand / hr$270.731$75.425
Spot / hr-$3.675
Prices in US East, N. Virginia

Compute

vCPUs896
Memory24576 GiB
Mem / vCPU27.43 GiB
ProcessorXeon Scalable
Clock speed2.9 GHz
Architecturex86_64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPSN/A
CoreMark / secN/A

Storage

TypeEBS only
Bandwidth100,000 Mbps
Throughput12500 MB/s
IOPS560,000
Base Bandwidth100,000 Mbps
Base Throughput12500 MB/s
Base IOPS560,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance200 Gigabit
Max ENIs16
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface106
IPs / ENI50
Baseline Bandwidth100 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 typeu7in-24tb.224xlarge
Full nameU7IN-24TB 224xlarge
FamilyMemory optimized
Variantu7in-24tb
GenerationCurrent
Bare MetalNo
EMR supportNo
DedicatedSupported
Introduced2024-05-29
Family sizes
u7in-24tb.224xlarge896 vCPU · 24576 GiB

u7in-24tb.224xlarge

The u7in-24tb.224xlarge is a memory-optimized AWS EC2 instance with 896 vCPU and 24576 GiB of memory. Rackspace Spot's largest server is 16 vCPU and 128 GiB, so matching this instance would take 175 × mh.vs1.2xlarge. That is arithmetically true and operationally absurd.

The Rackspace Spot column below prices that whole fleet, so read it as a scale reference rather than a drop-in replacement: at this size the useful question is what a shard of the workload costs, which is $0.021/hr per server.

Server comparison caveats
No single-node equivalent

The AWS u7in-24tb.224xlarge is 896 vCPU and 24,576 GiB. The largest comparable Rackspace Spot server is mh.vs1.2xlarge at 16 vCPU and 128 GiB, so matching it would take 175 of them. That maths works out, but 175 nodes is a redesign rather than a migration, because a single block of 24,576 GiB does not survive being split across a network.

If you chose u7in-24tb.224xlarge because the work genuinely needs 896 cores and 24,576 GiB together (an in-memory database, a large analytics engine, a single big solver), Rackspace Spot has no equivalent. What does fit is everything around it: the application servers, batch workers and CI that talk to that machine, which is usually the larger share of the bill.

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$270.731not offered$166.837$86.986$75.425$3.675
$195.306 (72%)
n/a
US Central, Chicagono AWS regionn/an/an/a$81.200$3.675n/an/a
US Central, Dallasno AWS regionn/an/an/a$81.025$22.925n/an/a
Hong Kongnot sold heren/an/an/a$86.450$3.675n/an/a
Sydney, Australianot sold heren/an/an/a$85.925$33.425n/an/a
London, UKnot sold heren/an/an/a$73.500$5.075n/an/a
US West, San Josenot sold heren/an/an/a$77.000$0.350n/an/a
US Central, Dallas 2no AWS regionn/an/an/a$77.000$42.350n/an/a

Prices updated 18 Nov 2026.

When to use it

Good for
  • ●OLAP and business intelligence query engines
  • ●Real-time analytics over hot datasets
  • ●Database instances that keep the working set in RAM
  • ●Workloads that fit inside 24576 GiB of RAM
  • ●Parallel work that can occupy 896 vCPU
  • ●Network-heavy services (AWS rates this size at 200 Gigabit)
Avoid if
  • ●The working set needs more than 24576 GiB of RAM
  • ●You want a single-machine Rackspace Spot equivalent. At this size there is not one.
  • ●GPU or FPGA acceleration is needed
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●More than 27.43 GiB of RAM per vCPU is needed, since that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 896 vCPU would sit idle.
u7in-24tb.224xlarge is $197,634/mo on AWS on-demand. A single mh.vs1.2xlarge is $315/mo on Rackspace Spot on-demand. At this size the per-server price is the honest comparison.
  • 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 u7in-24tb.224xlarge cost?

The AWS u7in-24tb.224xlarge costs $270.73/hr on-demand in US East (N. Virginia), about $197,634/mo running 24/7. On Rackspace Spot, 175 × mh.vs1.2xlarge is $75.42/hr on-demand, or $3.67/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 u7in-24tb.224xlarge per month?

At 730 hours a month, u7in-24tb.224xlarge in US East (N. Virginia) is $197,634/mo on AWS on-demand. The same capacity on Rackspace Spot (175 × mh.vs1.2xlarge) is $55,060/mo on-demand, or $2,683/mo at the Spot price. Rackspace Spot prices move with demand, so the Spot figure is a typical rate rather than a fixed one.

Can I replace u7in-24tb.224xlarge with Rackspace Spot?

Not as a single machine. Rackspace Spot's largest VM shape is 16 vCPU and 128 GiB, so it would take 175 × mh.vs1.2xlarge to reach 896 vCPU and 24576 GiB, and past roughly twenty nodes that stops being a credible substitution. Where the workload does shard (batch, web, queue consumers), a single mh.vs1.2xlarge at $0.021/hr is the number to compare against; the table's Rackspace Spot column prices the full 175-node fleet.

What is a cheaper alternative to u7in-24tb.224xlarge?

Rackspace Spot 175 × mh.vs1.2xlarge (2800 vCPU, 22400 GiB) is $55,060/mo on-demand or $2,683/mo at the Spot price, against $197,634/mo on-demand for u7in-24tb.224xlarge 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.