LLM GPU requirements

LLM GPU requirements: how much VRAM open models need

How much VRAM popular open models need to serve and fine-tune, and the cheapest servers that run them. Every number comes from the model’s published architecture and the same formulas as our VRAM calculator.

Configurations
15
Available now
13
From
$449/mo
Setup & egress fees
$0
GPU memory and the cheapest OverGPU server for each model
ModelParametersWeights FP8KV cache per 1k tokensTo serve 8k × 8 requestsCheapest server
Llama 3.1 8BMeta · Dense 8B 8.0 GB 131 MBBF16 27 GBBF16 $449NVIDIA GeForce RTX 5090
Qwen3 14BAlibaba Qwen · Dense 14.8B 15 GB 164 MBBF16 44 GBBF16 $1,390NVIDIA RTX PRO 6000 Blackwell
Mistral Small 24BMistral AI · Dense 23.6B 24 GB 164 MBBF16 38 GBFP8 $890NVIDIA L40S
Qwen3 32BAlibaba Qwen · Dense 32.8B 33 GB 262 MBBF16 54 GBFP8 $1,390NVIDIA RTX PRO 6000 Blackwell
Llama 3.3 70BMeta · Dense 70.6B 71 GB 328 MBBF16 100 GBFP8 $3,090NVIDIA H200
gpt-oss-120bOpenAI · Mixture of Experts 117B5.1B active 117 GB 37 MBBF16 68 GBMXFP4 (native 4-bit) $1,390NVIDIA RTX PRO 6000 Blackwell
Qwen3 235B-A22BAlibaba Qwen · Mixture of Experts 235B22B active 235 GB 193 MBBF16 272 GBFP8 $10,4908× NVIDIA RTX PRO 6000 Blackwell · PCIe, no NVLink
Llama 3.1 405BMeta · Dense 405B 405 GB 516 MBBF16 480 GBFP8 $10,4908× NVIDIA RTX PRO 6000 Blackwell · PCIe, no NVLink
DeepSeek-V3 / R1DeepSeek · Mixture of Experts 671B37B active 671 GB 70 MBMLA, BF16 Read the DeepSeek hardware guide

Swipe the table to see every column

Download these requirements as a CSV file.

Serving totals include the weights, a BF16 KV cache for 8 requests of 8k tokens and about 10% runtime overhead, with 8% of GPU memory kept free. Models split across GPUs run best on NVLink servers; the 8× RTX PRO 6000 server links its GPUs over PCIe. Prices in USD per month, excluding VAT.

How to estimate GPU requirements for any LLM

Three parts add up to the GPU memory a model needs to serve, and every page above computes them from the model's published architecture:

  • Weights Parameters × bytes per parameter: 2 bytes in BF16, 1 in FP8 and about 0.5 in 4-bit formats. A 70B model takes about 141 GB in BF16 and 71 GB in FP8.
  • KV cache 2 × layers × KV heads × head size × bytes per value, for every token in flight (see the glossary for the terms). It grows with the context length and with the number of concurrent requests.
  • Runtime overhead Activations, CUDA graphs and allocator fragmentation: plan on about 10% of the weights plus 1 GB, and keep some GPU memory free.

For a model that is not listed, enter its parameters, layers and KV heads in the VRAM calculator; it runs the same formulas and lists every configuration that fits.

Mixture-of-experts models: total parameters set the memory

A mixture-of-experts (MoE) model such as Qwen3 235B-A22B or gpt-oss-120b activates only a fraction of its parameters for each token, about 22B and 5.1B respectively, but every expert must sit in GPU memory. Size the weights from the total parameter count. The active count only sets the compute per token, which is why MoE models generate quickly once they fit.

Inference vs fine-tuning requirements

Fine-tuning needs more memory than serving. QLoRA keeps the base weights in 4-bit and trains small adapters; LoRA trains adapters on top of frozen BF16 weights; a full fine-tune with AdamW in mixed precision keeps weights, gradients and optimizer state for every parameter, about 16 bytes per parameter before activations. For a 70B model our estimates are about 53 GB with QLoRA, 175 GB with LoRA and about 1.36 TB for a full fine-tune, sharded across an 8-GPU server with FSDP or ZeRO-3. The 70B fine-tuning guide walks through each method.

Consumer vs data-center GPUs for LLMs

The GeForce RTX 5090 has 32 GB of GDDR7 at 1.8 TB/s: enough for 8B models in BF16, models up to about 32B at 4-bit with short contexts, and image generation, at the lowest monthly price. Data-center GPUs add capacity and bandwidth: 80 GB of HBM3 on the H100, 141 GB on the H200, 180 GB on the B200 and 288 GB on the B300 and MI355X, with NVLink or Infinity Fabric between the GPUs of an 8-GPU server so one model can span all eight. The RTX PRO 6000 Blackwell sits in between with 96 GB of GDDR7.

The rule of thumb: pick the smallest GPU whose memory holds the weights, the KV cache for your traffic and about 10% headroom, then compare monthly prices. The best GPU for LLM inference guide goes model size by model size.

Size any model

Enter parameters, precision, context and users to see the memory it needs and every configuration that fits.

Open the VRAM calculator Compare GPUs side by side

FAQ

LLM GPU requirements FAQ

The short version. The help center has the details, and customers with an active server get answers by ticket, 24/7.

Visit the help center
How much VRAM do I need to run a 70B model?

About 141 GB for the weights in BF16, 71 GB in FP8 and 35 GB at 4-bit, plus the KV cache and runtime overhead. In FP8, one H200 with 141 GB serves a 70B model with 8 concurrent requests at an 8k context.

Can I run an LLM on a single GPU?

Most models up to about 70B parameters run on one GPU in FP8 or 4-bit: 8B models on an RTX 5090, 32B models on an H100 and 70B models on an H200. Larger models such as Llama 3.1 405B or Qwen3 235B need an 8-GPU server.

How much does the KV cache add?

It depends on the model, the context and the number of users. For Llama 3.3 70B, the BF16 KV cache takes about 0.33 MB per token, so 32 requests at 32k tokens need about 340 GB on top of the weights.

Are these figures exact?

They are estimates from each model's published architecture with the same formulas as the VRAM calculator. Serving engines differ in overhead, so treat them as a sizing guide and check the free memory your engine reports at startup.

Deploy a GPU server

Not sure which server fits your model?

Choose a configuration, create your account in the same form and pay the first month from your balance. Your server is delivered in under 10 minutes.

  • Delivered in under 10 minutes
  • Cancel any month
  • Pay with crypto, up to +50% bonus

Log in to OverGPU

Manage your GPU servers, balance and invoices.

New to OverGPU? Create an account