Launch

Launch pricing: up to 74% below on-demand, fixed for your term — ends Oct 31, 2026 · 17d left Launch pricing ends Oct 31 · 17d left

See pricing

Llama · 70.6B parameters

Llama 3.3 70B: GPU memory requirements and which GPU to rent

Meta's Llama 3.3 70B is the most common large open model in production: 80 layers, grouped-query attention with 8 KV heads and a 128k-token context window. At 16-bit its weights alone exceed any 80 GB card; at FP8 they fit one 96 GB or 141 GB GPU.

  • Weights at FP871 GB141 GB at 16-bit · 39 GB at 4-bit
  • FP8, 8k context, 1 sequence78 GBweights + KV cache + runtime
  • Suggested here1× RTX PRO 6000$749 a month · dedicated

Inference

How much GPU memory Llama 3.3 70B needs to serve

Total memory for one sequence at each context length, and for 16 concurrent sequences at 8k — weights, KV cache at 16-bit and runtime overhead included.

Weights precisionWeights4k context32k context128k context8k × 16 sequencesSuggested here, 8k
16-bit (BF16 / FP16) 141 GB 150 GB 159 GB 191 GB 191 GB 2× RTX PRO 6000 · $1,498/mo
8-bit (FP8 / INT8) 71 GB 76 GB 86 GB 118 GB 118 GB 1× RTX PRO 6000 · $749/mo
4-bit (GPTQ, AWQ, Q4) 39 GB 43 GB 53 GB 85 GB 85 GB 1× L40S · $429/mo

GB are 109 bytes. Context lengths are shown for scale where the model supports them; an FP8 KV cache halves the cache part of each figure.

Hardware

GPU servers that run Llama 3.3 70B

For FP8 inference with an 8k context and one sequence: the configurations we would suggest, in order — one large card ahead of several small ones.

Fine-tuning Llama 3.3 70B

Memory for a 2k-token sequence and a micro-batch of 4, with gradient checkpointing. Full fine-tuning keeps gradients and Adam states for every parameter; LoRA and QLoRA train small adapters on a frozen base.

MethodMemorySuggested here
QLoRA, 4-bit base 67 GB 1× A100 · $649/mo
LoRA, 16-bit base 173 GB 2× RTX PRO 6000 · $1,498/mo
Full fine-tune, mixed precision 1,158 GB 8× B200 · $18,900/mo

Architecture at a glance

Parameters70.6Bdense: all active
Layers80hidden size 8,192
KV cache0.34 GBper 1,000 tokens at 16-bit

Grouped-query attention: every layer keeps keys and values for every token of the context. Figures from the model's published configuration; method on the calculator page.

Llama 3.3 70B hardware: questions answered

How much VRAM does Llama 3.3 70B need?

For the weights alone: about 141 GB at 16-bit, 71 GB at FP8 and 39 GB at 4-bit. Serving it at FP8 with an 8k-token context and one sequence takes about 78 GB in total once the KV cache and the runtime are counted; long contexts and many concurrent users add the KV cache on top — about 0.34 GB per 1,000 tokens at 16-bit.

Can Llama 3.3 70B run on a single GPU?

Yes, at FP8 with a moderate context: one NVIDIA RTX PRO 6000 Blackwell (96 GB GDDR7 ECC) holds it, for $749 a month here. Longer contexts or more concurrent users may need a larger card or a second GPU.

What is the cheapest GPU setup to run Llama 3.3 70B?

For FP8 inference with an 8k context and one sequence, the configuration we would suggest is 1× RTX PRO 6000 · $749/mo; at 4-bit, 1× L40S · $429/mo. Suggestions favour one large card over several small ones: splitting a model across PCIe cards costs speed.

How much GPU memory do I need to fine-tune Llama 3.3 70B?

With a 2k-token sequence and a micro-batch of 4: about 67 GB for QLoRA on a 4-bit base, 173 GB for LoRA on a 16-bit base, and 1,158 GB for a full fine-tune with Adam in mixed precision. Gradient checkpointing is assumed; sharding the optimizer across GPUs spreads the full fine-tune over several cards.

Run Llama 3.3 70B on 1× RTX PRO 6000 for $749 a month

Dedicated, single-tenant and live in under 10 minutes — with vLLM, the Hugging Face stack or Ollama preinstalled if you want. Paid in BTC, ETH or USDT, with no KYC.