Llama 3.1 70B on an H200
Yes, you can fine-tune Llama 3.1 70B on one H200 (141 GB) with QLoRA. 4-bit inference: yes, 40 GB of weights, room for 128K tokens of context or 64 concurrent 4K-token sequences.
Verdict by method
| Fine-tuning | Memory at 2K tokens | One H200? | Longest sequence (batch 1) | Largest batch at 2K | Largest LoRA rank |
|---|---|---|---|---|---|
| QLoRA (4-bit base) | 48 GB | Yes | 16K tokens | 15 | 256 |
| LoRA (16-bit base) | 150 GB | No | — | — | — |
| Full fine-tuning | 1,134 GB | No | — | — | n/a |
| Inference | Memory at 8K | One H200? | Longest context | Concurrent 4K sequences |
|---|---|---|---|---|
| 16-bit (BF16/FP16) | 144 GB | No | — | — |
| 8-bit | 73 GB | Yes | 128K tokens | 41 |
| 4-bit | 42 GB | Yes | 128K tokens | 64 |
- QLoRA: yes, about 48 GB at 2K tokens, batch 1, rank 16; up to 16K-token sequences at batch 1 or batch 15 at 2K, LoRA rank up to 256.
- LoRA: no, it needs about 150 GB at 2K tokens, more than the 141 GB available.
- Full fine-tuning: no, it needs about 1,134 GB at 2K tokens, more than the 141 GB available.
Where the memory goes
| Method | Weights | Training state | Activations | Total | On one H200 | 80 GB GPUs needed |
|---|---|---|---|---|---|---|
| QLoRA (4-bit base) | 40 GB | 3.3 GB | 5.6 GB | 48 GB | Fits | 1 |
| LoRA (16-bit base) | 141 GB | 3.3 GB | 5.6 GB | 150 GB | Doesn't fit | 3 |
| Full fine-tuning | 141 GB | 988 GB | 5.6 GB | 1,134 GB | Doesn't fit | 16 |
| Precision | Weights | KV cache at 8K | Total | At 128K context | On one H200 |
|---|---|---|---|---|---|
| 16-bit (BF16/FP16) | 141 GB | 2.7 GB | 144 GB | 184 GB | Doesn't fit |
| 8-bit | 71 GB | 2.7 GB | 73 GB | 114 GB | Fits |
| 4-bit | 40 GB | 2.7 GB | 42 GB | 83 GB | Fits |
The cheapest way to run it
Renting an H200 costs $5.29 an hour on Runpod Secure Cloud ($3.59 on Runpod Community Cloud). QLoRA on it processes about 1,093 tokens a second by our estimate, so 10 million training tokens take 2.5 hours and cost about $13.44.
| Job (default settings) | Memory | Cheapest rental that fits | Per hour |
|---|---|---|---|
| QLoRA fine-tuning | 48 GB | A100 80GB | $2.19 |
| LoRA fine-tuning | 150 GB | 4 × L40S | $4.36 |
| 4-bit inference | 42 GB | L40S | $1.09 |
| 16-bit inference | 144 GB | 2 × A100 80GB | $4.38 |
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. Kojen's GPU training can launch the H200 on Runpod, Vast.ai or Lambda, or pick the cheapest GPU in stock for you.
Try other settings
| Job | Memory | H200 (141 GB) | Smallest single GPU |
|---|---|---|---|
| QLoRA (4-bit base)2K tokens × batch 1, rank 16 | 48 GB | Fits | A100 80GB (80 GB) |
| LoRA (16-bit base)2K tokens × batch 1, rank 16 | 150 GB | 2 GPUs | B200 (180 GB) |
| Full fine-tuning2K tokens × batch 1 | 1,134 GB | 9 GPUs | None: needs several |
| Inference, 16-bit (BF16/FP16)8K-token context × 1 sequence | 144 GB | 2 GPUs | B200 (180 GB) |
| Inference, 8-bit8K-token context × 1 sequence | 73 GB | Fits | H200 (141 GB) |
| Inference, 4-bit8K-token context × 1 sequence | 42 GB | Fits | L40S (48 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 H200's dense BF16 peak of 989 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 Llama 3.1 70B on an H200?
- QLoRA: yes, about 48 GB at 2K tokens, batch 1, rank 16; up to 16K-token sequences at batch 1 or batch 15 at 2K, LoRA rank up to 256. LoRA: no, it needs about 150 GB at 2K tokens, more than the 141 GB available. Full fine-tuning: no, it needs about 1,134 GB at 2K tokens, more than the 141 GB available.
- Can I run Llama 3.1 70B on an H200?
- 16-bit (BF16/FP16) inference: no, the weights alone are 141 GB. 8-bit inference: yes, 71 GB of weights, room for 128K tokens of context or 41 concurrent 4K-token sequences. 4-bit inference: yes, 40 GB of weights, room for 128K tokens of context or 64 concurrent 4K-token sequences.
- What does fine-tuning Llama 3.1 70B on an H200 cost?
- With QLoRA at our planning rate of 40% utilisation, about 2.5 hours for 10 million training tokens, around $13.44 at $5.29 an hour (Runpod Secure Cloud, November 2026).
Related
- Llama 3.1 70B VRAM requirementsEvery GPU and method
- Llama 3.1 70B on RTX 409024 GB
- Llama 3.1 70B on RTX 509032 GB
- Llama 3.1 70B on A100 80GB80 GB
- Llama 3.1 70B on H100 SXM80 GB
- Llama 3.1 70B on B200180 GB
- Fine-tuning Llama 3.1 70B: costPer million tokens
- Llama 3.3 70B on H200Meta
- Qwen2.5 72B on H200Alibaba Qwen
- DeepSeek-R1-Distill-Llama-70B on H200DeepSeek
- gpt-oss-120b on H200OpenAI
Sources
- Hugging Face. meta-llama/Llama-3.1-70B-Instruct config.json
- Meta. meta-llama/Llama-3.1-70B-Instruct model card
- Meta. The Llama 3 Herd of Models (arXiv:2407.21783)
- NVIDIA. H200 specifications
- Runpod. GPU pricing (updated 12 November 2026)
- Lambda. GPU cloud pricing
- Dettmers et al., 2023. QLoRA: Efficient Finetuning of Quantized LLMs (arXiv:2305.14314)
- Hu et al., 2021. LoRA: Low-Rank Adaptation of Large Language Models (arXiv:2106.09685)
- Rajbhandari et al., 2019. ZeRO: Memory Optimizations Toward Training Trillion Parameter Models (arXiv:1910.02054)
- 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 Llama 3.1 70B is worth the GPU time.
Start training free