New B200 spot capacity is live in US East from $1.69 per GPU-hour. See availability →
Alibaba Qwen · Dense model · released September 2024

Qwen2.5 72B GPU requirements: 36.4 GB at 4-bit, 145 GB at BF16

Qwen2.5 72B needs 145 GB of GPU memory for its weights at BF16, 72.7 GB at FP8 and 36.4 GB at 4-bit, plus 10.7 GB of KV cache for a 32K context. The cheapest node that runs it here is 1× A100 PCIe 80GB at 4-bit, for $0.09 an hour on spot.

Architecture read from the model's config.json on Hugging Face, 26 October 2026 · prices from the live catalogue · all 47 GPUs

Cheapest node · 32K context per node-hour, spot
4-bit1× A100 PCIe 80GB · 47.1 GB needed $0.09$0.19 on-demand
FP82× L40 · 83.4 GB needed $0.18$0.38 on-demand
BF164× A40 · 156 GB needed $0.24$0.36 on-demand

Weights plus a 32K 16-bit KV cache, with 10% of the node's memory kept free. Billed per minute.

Parameters
72.7BDense
Weights, 4-bit
36.4 GBBF16: 145 GB
KV cache, 32K
10.7 GBOne sequence, 16-bit cache
Context window
128K32K native, extended with YaRN
Memory by format

How much VRAM Qwen2.5 72B needs, format by format.

Weights are parameters × bytes per parameter. Each context column adds the KV cache of one sequence of that length.

GPUs by memory
Format Weights + 8Kcontext+ 32Kcontext+ 128Kcontext Cheapest node, 32K
BF16Published weights, fine-tuning 145 GB 148 GB156 GB188 GB 4× A40 · $0.24/h
FP8Hopper, Ada, Blackwell, MI300 72.7 GB 75.4 GB83.4 GB116 GB 2× L40 · $0.18/h
4-bitAWQ, GPTQ, GGUF Q4 36.4 GB 39.0 GB47.1 GB79.3 GB 1× A100 PCIe 80GB · $0.09/h
Arithmetic on published facts, not a benchmark.

The serving engine adds its own buffers, and an 8-bit KV cache halves the context columns. We keep 10% of a node's memory free when we say a model fits. Speed is a separate question: it follows memory bandwidth and, for a mixture of experts, the active parameters.

Where it runs

GPUs that run Qwen2.5 72B, cheapest first.

For each format, the smallest node of each GPU model that holds the weights and a 32K context, sorted by spot price. One row per GPU model; larger nodes of the same GPU work too.

All prices
Format GPU GPU memory Spot On-demand 730 h spot Action
4-bit 1× A100 PCIe 80GBAmpere · 47.1 GB needed 80 GB $0.09 $0.19 $65.70 Deploy
4-bit 4× RTX A4000Ampere · 47.1 GB needed 64 GB $0.12 $0.20 $87.60 Deploy
4-bit 2× A40Ampere · 47.1 GB needed 96 GB $0.12 $0.18 $87.60 Deploy
4-bit 4× T4Turing · 47.1 GB needed 64 GB $0.16 $0.28 $116.80 Deploy
FP8 2× L40Ada Lovelace · 83.4 GB needed 96 GB $0.18 $0.38 $131.40 Deploy
FP8 2× RTX 6000 AdaAda Lovelace · 83.4 GB needed 96 GB $0.18 $0.38 $131.40 Deploy
FP8 1× RTX PRO 6000 BlackwellBlackwell · 83.4 GB needed 96 GB $0.19 $0.39 $138.70 Deploy
FP8 4× L4Ada Lovelace · 83.4 GB needed 96 GB $0.20 $0.32 $146.00 Deploy
BF16 4× A40Ampere · 156 GB needed 192 GB $0.24 $0.36 $175.20 Deploy
BF16 4× L40Ada Lovelace · 156 GB needed 192 GB $0.36 $0.76 $262.80 Deploy
BF16 4× RTX 6000 AdaAda Lovelace · 156 GB needed 192 GB $0.36 $0.76 $262.80 Deploy
BF16 4× RTX A6000Ampere · 156 GB needed 192 GB $0.36 $0.68 $262.80 Deploy

Spot capacity can be reclaimed with a 2-minute notice; for a live endpoint, use on-demand. How spot works · serving a language model.

Context and the KV cache

What a long context costs in memory.

Grouped-query attention, 8 KV heads of 128 across 80 layers.

Context KV cache, 1 sequence 8 sequences
8K tokens 2.68 GB 21.5 GB
32K tokens 10.7 GB 85.9 GB
128K tokens 42.9 GB 344 GB

Serving several users

KV cache

Every concurrent request keeps its own cache, so memory for context grows with users × context length. A server batching 8 requests of 32K needs eight times the single-sequence figure — 85.9 GB here.

  • Recommended node1× A100 PCIe 80GB
  • Weights at 4-bit36.4 GB
  • Context that fits, 1 sequence106K

Paged attention (vLLM, SGLang) allocates the cache in blocks as requests grow, so a node holds more short requests than the worst case suggests.

Model facts

Qwen2.5 72B, as published.

Developer
Alibaba QwenMultilingual dense model, long context with YaRN
Parameters
72.7B
Architecture
Dense model, 80 layersGrouped-query attention, 8 KV heads of 128 across 80 layers
Context window
131,072 tokens32,768 native, the rest with YaRN scaling
Published format
BF16, 145 GB
Licence
Custom licence (see the model card)
Released
19 September 2024
Source
Qwen/Qwen2.5-72B-Instructconfig.json read 26 October 2026

Serve it with vLLM

template: vLLM

On 1× A100 PCIe 80GB, from the instance terminal:

terminal
$ vllm serve Qwen/Qwen2.5-72B-Instruct \
    --tensor-parallel-size 1 \
    --max-model-len 32768

Very recent architectures need a recent vLLM; the model card gives the minimum version and any extra flags.

FAQ

Qwen2.5 72B on a GPU — the questions that come up

How much VRAM does Qwen2.5 72B need?

For the weights alone: 145 GB at BF16, 72.7 GB at FP8 and 36.4 GB at 4-bit. Add 10.7 GB of KV cache for one 32K-token context, or 42.9 GB at the full 128K window, and keep about 10% of the memory free for activations.

Can Qwen2.5 72B run on a single GPU?

One RTX 4090 (24 GB): no. One RTX 5090 (32 GB): no. One H100 SXM (80 GB): yes, at 4-bit. One H200 SXM (141 GB): yes, at FP8. One B200 SXM (180 GB): yes, at BF16. Those answers assume a 32K context and the widest format that still fits.

What is the cheapest way to run Qwen2.5 72B?

Here, 1× A100 PCIe 80GB at 4-bit: $0.09 per hour on spot and $0.19 on-demand, billed per minute — $65.70 for a 730-hour month on spot. That node has 80 GB of GPU memory for the 47.1 GB this setup needs.

How long a context fits on the recommended node?

With the weights at 4-bit on 1× A100 PCIe 80GB, the remaining memory holds a 16-bit KV cache for about 108,779 tokens of context for one sequence (106K). An 8-bit KV cache doubles that; serving several users at once divides it between them.

Which format should I run it in?

BF16 keeps the published weights untouched and is the format for fine-tuning. FP8 halves the memory and runs in hardware on Hopper, Ada, Blackwell and MI300-class GPUs. 4-bit quantisation (AWQ, GPTQ, GGUF) quarters it, at a quality cost that is larger on small models than on big ones; check it against your own evaluation before relying on it.

How do I deploy it?

Pick the node in the table above and launch it with the vLLM template; the model downloads from Hugging Face (Qwen/Qwen2.5-72B-Instruct) on first start. Spread the weights over the node with --tensor-parallel-size equal to the GPU count, and set --max-model-len to the context you need. New architectures need a recent vLLM: check the model card for the minimum version.

Sizing another model? GPU requirements for 64 open models · serving a language model · fine-tuning.

Get started

Qwen2.5 72B on 1× A100 PCIe 80GB for $0.09 an hour.

Launch the node with the vLLM template, point it at Qwen/Qwen2.5-72B-Instruct, stop it when you are done. Prepaid, billed by the minute.

Billed per minute from the moment the instance is reachable. Minimum credit $30, no subscription.