- Teams comparing GPU families
- LLM pilots before a capacity request
- Budget planning with explicit assumptions
- Explaining a hardware choice to reviewers
GPU selection guide
How to choose a cloud GPU for an LLM.
Choose an LLM GPU in this order: define the task, calculate weight and runtime memory, add KV cache or training state, set latency or deadline targets, then benchmark the smallest compatible GPU. Compare total cost per accepted outcome. The newest or fastest GPU is not automatically the most economical.
Reviewed by the GPURento infrastructure team · September 1, 2026
| Step 1 | Define the task | Inference, LoRA, full tuning and training differ. |
|---|---|---|
| Step 2 | Estimate peak memory | Include runtime state and headroom. |
| Step 3 | Set service target | Latency, throughput, deadline and quality. |
| Step 4 | Benchmark total cost | Measure an accepted result end to end. |
- Replacing an end-to-end benchmark
- Assuming parameter count equals total memory
- Selecting from peak FLOPS alone
Decision method
What to verify before you deploy capacity.
The content below separates published specifications, GPURento catalog references and decisions that still require a workload benchmark.
1. Start with the workload mode
Inference stores weights and runtime state; training adds gradients, optimizer states and activations; parameter-efficient tuning sits between them. Write down model revision, precision, context or sequence length, batch and concurrency before comparing hardware.
2. Build a memory budget
A rough weight estimate is parameters multiplied by bytes per parameter, but kernels, quantization metadata, KV cache, activations and fragmentation add overhead. Treat any calculator as a shortlist, then validate peak allocation.
- Add 10–20% operational headroom as a starting assumption
- Do not mix decimal GB and binary GiB silently
- Retest after changing context, batch or runtime
3. Compare outcomes, not specifications
For inference compare latency and dollars per million accepted tokens. For training compare time and dollars per accepted checkpoint. For visual work compare cost per accepted image, clip or frame.
Catalog shortlist
Relevant GPU options.
NVIDIA RTX 4090
24 GB GDDR6X · $0.34/hr
Image, video and mid-size inference
NVIDIA RTX 5090
32 GB GDDR7 · $0.69/hr
Fast single-GPU inference and media
NVIDIA A100 80GB
80 GB HBM2e · $1.19/hr
Training, fine-tuning and HPC
NVIDIA H100 SXM
80 GB HBM3 · $2.69/hr
Intensive training and FP8 inference
NVIDIA H200 SXM
141 GB HBM3e · $3.59/hr
Large-model inference and HPC
Questions
Clear answers, including the limits.
How much GPU memory does an LLM need?+
At minimum, weights must fit at the selected precision. Add runtime workspace and KV cache for inference, or gradients, optimizer state and activations for training.
Should I always choose the GPU with the most VRAM?+
No. Extra memory is valuable only when it avoids an actual constraint. A smaller GPU can be cheaper when the workload fits and meets the performance target.
Can a selector guarantee compatibility?+
No. It can produce a shortlist from transparent assumptions, but the exact model, runtime and container must be tested.
- NVIDIA A100 product pageA100 architecture and 80 GB configuration from the manufacturer.
- NVIDIA H100 product pageArchitecture and memory specifications from the manufacturer.
- NVIDIA H200 product pageH200 memory capacity and bandwidth from the manufacturer.
Last reviewed September 1, 2026. GPURento rates are current catalog references; provisioning state remains visible in the workspace, and manufacturer specifications do not substitute for workload benchmarks.
Continue the research
Deployment plan
Use the shortlist, then run a pilot.
The selector narrows the catalog; a funded workspace request turns the chosen configuration into a testable plan.