Won't fitfp16 · 4K ctx · batch 1

Does L40S run Qwen2.5-72B? No at fp16.

At fp16 precision, Qwen2.5-72B (72 B parameters) needs roughly 164.1 GB of VRAM. L40S only has 48 GB, short by 116.1 GB. INT4 quantization brings it down to 44.6 GB — that fits.

342%
VRAM
Won't fit
Estimated VRAM (fp16)
164.1 GB
of 48 GB on L40S· 116.1 GB short
Tok/sec
37
TFTT
1790ms
Power
223W
Rent on GPUniq marketplace
L40S
Live prices from verified providers · billed hourly, no commitment.
Rent now

Memory breakdown (fp16)

Model Weights
144.00 GB
KV Cache
3.75 GB
Activations
15.00 GB
Framework Overhead
1.36 GB

Quantization comparison

Lower precision = less VRAM with a small quality trade-off. Quality order: FP16 > INT8 > INT4.

PrecisionVRAMUtilisationFits on L40S?
FP16 (full precision)164.1 GB342%Won't fit
INT8 (8-bit)84.4 GB176%Won't fit
INT4 / Q4 (4-bit)44.6 GB93%⚠️Tight fit

Frequently asked

Can L40S run Qwen2.5-72B?
Not at fp16 — Qwen2.5-72B needs about 164.1 GB while L40S has 48 GB. It fits at INT4 quantization (44.6 GB) with some accuracy trade-off.
How much VRAM does Qwen2.5-72B use?
About 164.1 GB at fp16, 44.6 GB at INT4 (for a 4K context, batch size 1). Longer contexts add to KV cache size; larger batches increase activations.
What's the fastest way to run Qwen2.5-72B on L40S?
Use a production inference engine like vLLM, SGLang, or TensorRT-LLM with paged attention — they cut KV cache 2–3× vs the naive estimate and batch multiple requests efficiently. For L40S, enable Flash Attention 2.
Where can I rent a L40S?
GPUniq aggregates live L40S offers from verified providers. You can deploy an instance in about a minute and pay hourly with no commitment.
Try it live

Chat with Qwen2.5-72B — no setup

Send a prompt and see how Qwen2.5-72B responds directly in our chat. No installation, no GPU required to test.

Open in chat
Want to tweak sequence length, batch size, or fine-tuning? Open the full calculator →