RTX A6000 vs RTX A5000
Both run on the same nodes, the same templates and the same tiers here — so the choice comes down to memory, bandwidth and price. Every figure below is from the catalogue or the vendor datasheet.
- RTX A6000
- $0.09/h48 GB · Ampere · 48 available
- RTX A5000
- $0.06/h24 GB · Ampere · 48 available
- Price gap
- 33%On spot, per GPU-hour
- Over 100 h
- $3.00Difference for the same GPU-hours
What actually separates them.
Four differences that change a decision, computed from the numbers rather than asserted.
Bigger models fit on the RTX A6000
48 GB against 24 GB. At FP16 that is about 19B parameters on one GPU, against 9B.
The RTX A5000 costs 33% less per hour
$0.06 against $0.09 on spot — $3.00 of difference over 100 GPU-hours.
More memory per dollar on the RTX A6000
533 GB per dollar per hour against 400 GB. The usual tie-breaker when both cards fit the job.
Every figure we hold on both cards.
A row is marked only when both values exist and one is genuinely better. RTX A6000 leads on 3 rows, RTX A5000 on 4.
| RTX A6000 | RTX A5000 | |
|---|---|---|
| GPU memoryDecides which models fit at all | 48 GB GDDR6 | 24 GB GDDR6 |
| Memory bandwidthSets token throughput on inference | 768 GB/s | 768 GB/s |
| FP32 | 39 TFLOPS | 28 TFLOPS |
| 8-bit float (FP8)Halves the memory a model needs, where the stack supports it | Not supported | Not supported |
| Architecture | Ampere (2020) | Ampere (2021) |
| Board powerLower is cheaper to run at scale — for us, not for your bill | 300 W | 230 W |
| GPU-to-GPU linkOnly matters for multi-GPU training | NVLink | NVLink |
| Node sizes | 1×, 2×, 4× | 1×, 2×, 4× |
| Spot price | $0.09/h | $0.06/h |
| On-demand price | $0.17/h | $0.09/h |
| Memory per dollarGPU memory per $1 of spot time, per hour | 533 GB | 400 GB |
| 30-day reclaim rateShare of spot instances reclaimed | <5% | <5% |
| Available now | 48 GPUs | 48 GPUs |
Specifications come from each vendor's datasheet — linked on the RTX A6000 page and the RTX A5000 page. Prices are ours, per GPU-hour, billed per minute.
The same models, on one GPU of each.
Weights only, with 20% of the memory kept free for activations and the KV cache. A cross means one GPU is not enough — the model page has the multi-GPU arithmetic.
| Model | Precision | RTX A6000 48 GB | RTX A5000 24 GB |
|---|---|---|---|
| Llama 3.1 8B8B parameters | FP16 · 16 GB | Fits | Fits |
| INT4 · 4 GB | Fits | Fits | |
| Qwen2.5 32B32B parameters | FP16 · 64 GB | Needs 2× node | Needs 4× node |
| INT4 · 16 GB | Fits | Fits | |
| Llama 3.3 70B70B parameters | FP16 · 140 GB | Needs 4× node | Needs more than one node |
| INT4 · 35 GB | Fits | Needs 2× node | |
| Mixtral 8x22B141B parameters | FP16 · 282 GB | Needs more than one node | Needs more than one node |
| INT4 · 71 GB | Needs 2× node | Needs 4× node |
The same 100 GPU-hours on each.
Compute only, billed per minute. Storage is $0.08 per GB-month on either card.
| RTX A6000 | RTX A5000 | |
|---|---|---|
| One hour, spot | $0.09 | $0.06 |
| One day, spot | $2.16 | $1.44 |
| 100 GPU-hours, spot | $9.00 | $6.00 |
| 100 GPU-hours, on-demand | $17.00 | $9.00 |
| A month, reserved | $65.70 | $43.80 |
Take the RTX A6000 when…
- Fine-tuning with LoRA and QLoRA — Comfortable for parameter-efficient training on 13B–34B models without sharding.
- Inference servers — Holds 30B-class models quantised, or several smaller models side by side.
- Multi-GPU jobs over NVLink — GPU-to-GPU traffic stays off the PCIe bus, which is what makes tensor and pipeline parallelism worth it.
Take the RTX A5000 when…
- Fine-tuning small models — LoRA on 7B–13B models, and full fine-tuning below 3B.
- Image and video generation — Diffusion pipelines run entirely in memory at this capacity.
- Multi-GPU jobs over NVLink — GPU-to-GPU traffic stays off the PCIe bus, which is what makes tensor and pipeline parallelism worth it.
RTX A6000 or RTX A5000?
Which is cheaper, the RTX A6000 or the RTX A5000?
The RTX A5000, at $0.06 per GPU-hour on spot against $0.09 — 33% less. On-demand: $0.09 against $0.17.
Which one should I take for inference?
Take the one that holds the model with room for the KV cache, then the one with more memory bandwidth. Here that is the RTX A6000 on capacity (48 GB) and the RTX A6000 on bandwidth.
Can I run both on the same job?
Not inside one instance — a node holds GPUs of a single model. You can run two instances in parallel, on the same persistent volume in turn, or split the work: a big card for the model that needs capacity, a cheap one for the parts that do not.
Other comparisons: the full list · all 47 models
Try both for less than the price of deciding.
An hour on each costs $0.15 on spot. Nothing renews, and your disk moves between them.
Billed per minute from the moment the instance is reachable. Minimum credit $40, no subscription.