AWS EC2 Instances›General Purpose›m7g›m7g.16xlarge

Compared with Rackspace Spot

AWSRackspace Spot
Machinem7g.16xlarge4 × gp.vs2.2xlarge
vCPU6464
Memory256 GiB256 GiB
Local diskNoneNone
On-demand / hr$3.046$1.400
Spot / hr$0.691$0.604
Prices in US West, San Jose

Compute

vCPUs64
Memory256 GiB
Mem / vCPU4.00 GiB
ProcessorGraviton3 Processor
Clock speed2.5 GHz
Architecturearm64
GPU0
GPU Wattage0 W
GPU ArchitectureNone
Video Memory0 GiB
FPGA0
ffmpeg FPS242
CoreMark / sec1,580,052

Storage

TypeEBS only
Bandwidth20,000 Mbps
Throughput2500 MB/s
IOPS80,000
Base Bandwidth20,000 Mbps
Base Throughput2500 MB/s
Base IOPS80,000
Devices0
NVMe DriveNo
SSDNo
Swap PartitionNo

Networking

Performance30 Gigabit
Max ENIs15
IPv6Yes
GPUNone
Placement GroupSupported
TrunkingYes
Branch Interface107
IPs / ENI50
Baseline Bandwidth30 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 typem7g.16xlarge
Full nameM7G 16xlarge Extra Large
FamilyGeneral purpose
Variantm7g
GenerationCurrent
Bare MetalNo
EMR supportYes
DedicatedSupported
Introduced2023-02-13
Family sizes

m7g.16xlarge

The m7g.16xlarge is a general-purpose AWS EC2 instance with 64 vCPU and 256 GiB of memory. In US East (N. Virginia), the closest Rackspace Spot server is gp.vs1.2xlarge at 16 vCPU and 64 GiB, so you will need 4 of them to get a total of 64 vCPU and 256 GiB.

Even with 4 servers, Rackspace Spot's on-demand price is about 53% below AWS on-demand and its Spot market price is about 86% 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 m7g.16xlarge gives you 64 vCPU and 256 GiB in a single machine. The largest comparable Rackspace Spot server, gp.vs2.2xlarge, is 16 vCPU and 64 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 256 GiB in one process, it does not.

x86_64 only

The AWS m7g.16xlarge 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, so it is worth testing before you decide how many nodes to run.

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$2.611$1.183$1.727$1.184$1.216$0.164
$1.395 (53%)
$1.019 (86%)
US Central, Chicagono AWS regionn/an/an/a$1.344$0.044n/an/a
US Central, Dallasno AWS regionn/an/an/a$1.292$0.324n/an/a
Hong Kong$3.590$0.754$2.375$1.629$1.356$0.044
$2.234 (62%)
$0.710 (94%)
Sydney, Australia$3.264$1.008$2.159$1.480$1.276$0.164
$1.988 (61%)
$0.845 (84%)
London, UK$3.019$0.541$1.994$1.373$1.156$0.524
$1.863 (62%)
$0.017 (3%)
US West, San Jose$3.046$0.691$2.009$1.388$1.400$0.604
$1.646 (54%)
$0.087 (13%)
US Central, Dallas 2no AWS regionn/an/an/a$1.360$0.004n/an/a
US East, N. Virginia 2$2.611$1.183$1.727$1.184$1.400$0.764
$1.211 (46%)
$0.419 (35%)

Prices updated 18 Nov 2026.

When to use it

Good for
  • ●Backend services with no single dominant resource
  • ●Queue workers and scheduled jobs
  • ●Web and application servers with mixed CPU and memory demand
  • ●Workloads that fit inside 256 GiB of RAM
  • ●Parallel work that can occupy 64 vCPU
  • ●Network-heavy services (AWS rates this size at 30 Gigabit)
  • ●Anything that shards cleanly across 4 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m8g.16xlarge is the newer generation at this size.
  • ●The working set needs more than 256 GiB of RAM
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
m7g.16xlarge is $1,906/mo on AWS on-demand and $888/mo on Rackspace Spot on-demand for 4 servers, 53% 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 m7g.16xlarge cost?

The AWS m7g.16xlarge costs $2.61/hr on-demand in US East (N. Virginia), about $1,906/mo running 24/7, or $1.18/hr at the AWS Spot price. On Rackspace Spot, 4 × gp.vs2.2xlarge is $1.22/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 m7g.16xlarge per month?

At 730 hours a month, m7g.16xlarge in US East (N. Virginia) is $1,906/mo on AWS on-demand, or $864/mo at the AWS Spot price. The same capacity on Rackspace Spot (4 × gp.vs2.2xlarge) is $888/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 m7g.16xlarge?

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

Is m7g.16xlarge ARM or x86?

ARM. m7g.16xlarge runs on AWS Graviton3 Processor, so its binaries and container images are aarch64. Rackspace Spot's gp.vs2.2xlarge is x86-64, which means this is a substitution and not a migration: anything not already built multi-arch has to be rebuilt before it runs. For interpreted stacks that is usually a rebuild of the base image; for anything with native extensions, check them individually.

Is m7g.16xlarge still worth using?

For workloads already running on it, yes: it works and it is priced accordingly. For anything new, m8g.16xlarge is the current answer and measures roughly 23% more CoreMark throughput at the same vCPU count. 2 newer generations of the m family have shipped since (m8g and m9g), which is the signal that matters for infrastructure you expect to keep running.

What is the difference between m7g and m8g?

m8g is the newer generation. It runs on AWS Graviton4 Processor against m7g's AWS Graviton3 Processor. On the CoreMark figures in this dataset, m8g.16xlarge scores 1,941,748 per second against m7g.16xlarge's 1,580,052. On-demand in US East (N. Virginia) the newer size is 10% more expensive. Neither generation changes the Rackspace Spot side: both map to the same Rackspace Spot servers.