The m6g.8xlarge is a general-purpose AWS EC2 instance: 32 vCPU and 128 GiB of memory, 4.00 GiB per vCPU. In the name, "m" is the general-purpose line, "6" is the generation, "g" marks AWS Graviton (ARM) processors and "8xlarge" is the size within the m6g family. It runs on AWS Graviton2 Processor at 2.5 GHz, and AWS introduced it in May 2020. AWS has since shipped m7g, m8g and m9g; m7g.8xlarge is the direct replacement at this size, scoring 815,390 CoreMark/s against this instance's 627,861 — roughly 30% more throughput for the same vCPU count. No single Spot node covers 32 vCPU and 128 GiB, so the equivalent is a fleet: 2 × gp.vs2.2xlarge, 32 vCPU and 128 GiB in total, about 93% 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
m6g.8xlarge gives you 32 vCPU and 128 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 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 128 GiB in one process, it does not.
x86_64 onlym6g.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.
