Skip to content

VRAM reference

Qwen2.5 7B on an RTX 5090

Yes, you can fine-tune Qwen2.5 7B on one RTX 5090 (32 GB) with QLoRA or LoRA. 4-bit inference: yes, 4.3 GB of weights, room for 128K tokens of context or 104 concurrent 4K-token sequences.

By Will Schulz · Checked 15 November 2026 · Prices as of November 2026

Verdict by method

Fine-tuningMemory at 2K tokensOne RTX 5090?Longest sequence (batch 1)Largest batch at 2KLargest LoRA rank
QLoRA (4-bit base)9.5 GBYes8K tokens6256
LoRA (16-bit base)19 GBYes4K tokens3128
Full fine-tuning125 GBNo——n/a
InferenceMemory at 8KOne RTX 5090?Longest contextConcurrent 4K sequences
16-bit (BF16/FP16)16 GBYes128K tokens57
8-bit8.1 GBYes128K tokens90
4-bit4.8 GBYes128K tokens104
  • QLoRA: yes, about 9.5 GB at 2K tokens, batch 1, rank 16; up to 8K-token sequences at batch 1 or batch 6 at 2K, LoRA rank up to 256.
  • LoRA: yes, about 19 GB at 2K tokens, batch 1, rank 16; up to 4K-token sequences at batch 1 or batch 3 at 2K, LoRA rank up to 128.
  • Full fine-tuning: no, it needs about 125 GB at 2K tokens, more than the 32 GB available.

Where the memory goes

At 2,048 tokens per sequence, batch 1, LoRA rank 16, gradient checkpointing on
MethodWeightsTraining stateActivationsTotalOn one RTX 509080 GB GPUs needed
QLoRA (4-bit base)5.5 GB0.6 GB3.3 GB9.5 GBFits1
LoRA (16-bit base)15 GB0.6 GB3.3 GB19 GBFits1
Full fine-tuning15 GB107 GB3.3 GB125 GBDoesn't fit2
One sequence, fp16 KV cache
PrecisionWeightsKV cache at 8KTotalAt 128K contextOn one RTX 5090
16-bit (BF16/FP16)15 GB0.5 GB16 GB23 GBFits
8-bit7.6 GB0.5 GB8.1 GB15 GBFits
4-bit4.3 GB0.5 GB4.8 GB12 GBFits

The cheapest way to run it

Renting an RTX 5090 costs $1.39 an hour on Runpod Secure Cloud ($0.69 on Runpod Community Cloud). LoRA on it processes about 2,751 tokens a second by our estimate, so 10 million training tokens take 1.0 hours and cost about $1.40.

Job (default settings)MemoryCheapest rental that fitsPer hour
QLoRA fine-tuning9.5 GBRTX 3090$0.50
LoRA fine-tuning19 GBRTX 3090$0.50
4-bit inference4.8 GBRTX 3090$0.50
16-bit inference16 GBRTX 3090$0.50

On-demand rates seen on 15 November 2026: Runpod Secure Cloud, Lambda for the A100 40GB. Consumer cards count as single GPUs only; data-centre GPUs up to eight per node.

Try other settings

JobMemoryRTX 5090 (32 GB)Smallest single GPU
QLoRA (4-bit base)2K tokens × batch 1, rank 169.5 GBFitsRTX 3090 (24 GB)
LoRA (16-bit base)2K tokens × batch 1, rank 1619 GBFitsRTX 3090 (24 GB)
Full fine-tuning2K tokens × batch 1125 GB5 GPUsH200 (141 GB)
Inference, 16-bit (BF16/FP16)8K-token context × 1 sequence16 GBFitsRTX 3090 (24 GB)
Inference, 8-bit8K-token context × 1 sequence8.1 GBFitsRTX 3090 (24 GB)
Inference, 4-bit8K-token context × 1 sequence4.8 GBFitsRTX 3090 (24 GB)

A job fits when the estimate is within 90% of the card's memory. Training assumes gradient checkpointing and FlashAttention; multi-GPU counts assume the memory splits evenly (FSDP, ZeRO-3 or tensor parallelism).

How we estimate it

Every figure comes from the model's published architecture (layers, hidden size, attention and KV heads, vocabulary) rather than a rule of thumb, using the same functions as the calculator above. Sizes are in GB (10⁹ bytes).

  • Full fine-tuning: 16 bytes per parameter for mixed-precision Adam (bf16 weights and gradients, fp32 master weights and two moments), as in the ZeRO paper.
  • LoRA: frozen bf16 weights (2 bytes per parameter) plus 16 bytes per adapter parameter, rank 16 on every linear layer. For mixture-of-experts models, adapters go on attention only and the experts stay frozen.
  • QLoRA: NF4 weights with double quantisation (4.127 bits per parameter); embeddings and the output head stay in bf16, as bitsandbytes leaves them.
  • Activations: gradient checkpointing and FlashAttention. Each layer's bf16 input is kept, one layer is recomputed at a time, and the output logits take 8 bytes per vocabulary entry per token (fp32 values and gradients). Chunked cross-entropy, as in Unsloth or Liger kernels, cuts that last term.
  • Inference: 2, 1 or about 0.56 bytes per weight (4-bit with group-wise scales), plus an fp16 KV cache of 2 × layers × KV heads × head dim × 2 bytes per token; sliding-window layers only cache their window.
  • Fits means the estimate is within 90% of the card's listed memory; the rest covers the CUDA context, kernels and fragmentation. Multi-GPU counts assume memory splits evenly.

Speed estimates use RTX 5090's dense BF16 peak of 209.5 TFLOPS, about 4 FLOPs per active parameter per token for LoRA and 40% utilisation; see fine-tuning and training costs for the method.

Frequently asked questions

Can I fine-tune Qwen2.5 7B on an RTX 5090?
QLoRA: yes, about 9.5 GB at 2K tokens, batch 1, rank 16; up to 8K-token sequences at batch 1 or batch 6 at 2K, LoRA rank up to 256. LoRA: yes, about 19 GB at 2K tokens, batch 1, rank 16; up to 4K-token sequences at batch 1 or batch 3 at 2K, LoRA rank up to 128. Full fine-tuning: no, it needs about 125 GB at 2K tokens, more than the 32 GB available.
Can I run Qwen2.5 7B on an RTX 5090?
16-bit (BF16/FP16) inference: yes, 15 GB of weights, room for 128K tokens of context or 57 concurrent 4K-token sequences. 8-bit inference: yes, 7.6 GB of weights, room for 128K tokens of context or 90 concurrent 4K-token sequences. 4-bit inference: yes, 4.3 GB of weights, room for 128K tokens of context or 104 concurrent 4K-token sequences.
What does fine-tuning Qwen2.5 7B on an RTX 5090 cost?
With LoRA at our planning rate of 40% utilisation, about 1.0 hours for 10 million training tokens, around $1.40 at $1.39 an hour (Runpod Secure Cloud, November 2026).

Sources

  1. [1]Hugging Face. Qwen/Qwen2.5-7B-Instruct config.json
  2. [2]Alibaba Qwen. Qwen/Qwen2.5-7B-Instruct model card
  3. [3]Alibaba Qwen. Qwen2.5 Technical Report (arXiv:2412.15115)
  4. [4]NVIDIA. RTX 5090 specifications
  5. [5]Runpod. GPU pricing (updated 12 November 2026)
  6. [6]Lambda. GPU cloud pricing
  7. [7]Dettmers et al., 2023. QLoRA: Efficient Finetuning of Quantized LLMs (arXiv:2305.14314)
  8. [8]Hu et al., 2021. LoRA: Low-Rank Adaptation of Large Language Models (arXiv:2106.09685)
  9. [9]Rajbhandari et al., 2019. ZeRO: Memory Optimizations Toward Training Trillion Parameter Models (arXiv:1910.02054)
  10. [10]Korthikanti et al., 2022. Reducing Activation Recomputation in Large Transformer Models (arXiv:2205.05198)

Measure before you rent the GPU.

Prompt tuning and model search in Kojen run on hosted models against your own test cases, so you know whether fine-tuning Qwen2.5 7B is worth the GPU time.

Start training free