GPU selection guide

How to choose a cloud GPU for an LLM.

Direct answer

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

Key facts for How to choose a cloud GPU for an LLM.
Step 1Define the taskInference, LoRA, full tuning and training differ.
Step 2Estimate peak memoryInclude runtime state and headroom.
Step 3Set service targetLatency, throughput, deadline and quality.
Step 4Benchmark total costMeasure an accepted result end to end.
Best for
  • Teams comparing GPU families
  • LLM pilots before a capacity request
  • Budget planning with explicit assumptions
  • Explaining a hardware choice to reviewers
Not the best fit when
  • 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.

01

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.

02

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
03

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.

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.

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.