Llama 2 70B FP16 Model Size 140GB Guide

💡 Quick Answer: Llama 2 70B in FP16 precision requires ~140GB of VRAM (70 billion parameters × 2 bytes). A single H200 (141GB) can fit it. For H100 (80GB), use 2× GPUs with tensor parallelism. FP8 halves to ~70GB (1× H100), and INT4/GPTQ reduces to ~35GB (1× A100 40GB).

The Problem

Before deploying Llama 2 70B (or any large model) on Kubernetes, you need to calculate VRAM requirements to choose the right GPU type, count, and parallelism strategy. Getting this wrong means either OOM crashes or wasted GPU spend.

flowchart TB
    PARAMS["70B Parameters"] --> FP16["FP16: 70B × 2 bytes<br/>= 140 GB"]
    PARAMS --> FP8["FP8: 70B × 1 byte<br/>= 70 GB"]
    PARAMS --> INT4["INT4: 70B × 0.5 bytes<br/>= 35 GB"]
    FP16 --> H200["1× H200 (141GB)<br/>or 2× H100 (80GB)"]
    FP8 --> H100["1× H100 (80GB)<br/>or 2× A100 (40GB)"]
    INT4 --> A100["1× A100 40GB<br/>or 1× L40S (48GB)"]

The Solution

Model Size Formula

VRAM = Parameters × Bytes per Parameter + Overhead

Bytes per precision:
  FP32:  4 bytes
  FP16:  2 bytes (BF16 same)
  FP8:   1 byte
  INT4:  0.5 bytes (GPTQ/AWQ)

Overhead: ~10-20% for KV cache, activations, CUDA kernels

Llama Model Family Sizes

GPU Memory Reference

Kubernetes Deployment by GPU

1× H200 — FP16 (Best Quality)

apiVersion: apps/v1
kind: Deployment
metadata:
  name: llama-70b-fp16
spec:
  replicas: 1
  template:
    spec:
      containers:
        - name: vllm
          image: vllm/vllm-openai:latest
          args:
            - --model=meta-llama/Llama-2-70b-chat-hf
            - --dtype=float16
            - --tensor-parallel-size=1
            - --max-model-len=4096
            - --gpu-memory-utilization=0.90
          resources:
            limits:
              nvidia.com/gpu: 1
          env:
            - name: HF_TOKEN
              valueFrom:
                secretKeyRef:
                  name: hf-token
                  key: token
      nodeSelector:
        nvidia.com/gpu.product: NVIDIA-H200

2× H100 — FP16 with Tensor Parallelism

apiVersion: apps/v1
kind: Deployment
metadata:
  name: llama-70b-fp16-tp2
spec:
  replicas: 1
  template:
    spec:
      containers:
        - name: vllm
          image: vllm/vllm-openai:latest
          args:
            - --model=meta-llama/Llama-2-70b-chat-hf
            - --dtype=float16
            - --tensor-parallel-size=2
            - --max-model-len=4096
            - --gpu-memory-utilization=0.90
          resources:
            limits:
              nvidia.com/gpu: 2
          env:
            - name: HF_TOKEN
              valueFrom:
                secretKeyRef:
                  name: hf-token
                  key: token
      nodeSelector:
        nvidia.com/gpu.product: NVIDIA-H100-80GB-HBM3

1× H100 — FP8 (Best Balance)

args:
  - --model=meta-llama/Llama-2-70b-chat-hf
  - --dtype=float16
  - --quantization=fp8
  - --tensor-parallel-size=1
  - --max-model-len=4096
resources:
  limits:
    nvidia.com/gpu: 1
nodeSelector:
  nvidia.com/gpu.product: NVIDIA-H100-80GB-HBM3

1× A100 40GB — INT4 GPTQ (Most Affordable)

args:
  - --model=TheBloke/Llama-2-70B-Chat-GPTQ
  - --quantization=gptq
  - --tensor-parallel-size=1
  - --max-model-len=2048    # Reduced for 40GB
  - --gpu-memory-utilization=0.95
resources:
  limits:
    nvidia.com/gpu: 1
nodeSelector:
  nvidia.com/gpu.product: NVIDIA-A100-SXM4-40GB

KV Cache Memory Impact

Model weights are just part of the story. KV cache grows with context length and batch size:

KV Cache per token = 2 × num_layers × num_kv_heads × head_dim × bytes_per_param

Llama 2 70B (FP16):
  KV per token = 2 × 80 × 8 × 128 × 2 bytes = 327,680 bytes ≈ 0.31 MB

Context 4096 tokens × batch 16:
  KV cache = 4096 × 16 × 0.31 MB ≈ 20 GB

Total VRAM = Model (140 GB) + KV Cache (20 GB) + Overhead ≈ 168 GB

This is why a single H200 (141GB) can load the model but may need reduced batch size for long contexts.

Quick Sizing Decision Matrix

Common Issues

Best Practices

• Start with FP8 on H100/H200 — best quality-per-VRAM ratio
• Use tensor parallelism, not pipeline parallelism for inference — lower latency
• Set `—gpu-memory-utilization=0.90` — leaves headroom for KV cache spikes
• Pre-download models to PersistentVolumes — avoid cold-start download delays
• Use NVLink for multi-GPU — PCIe bottlenecks tensor parallelism significantly
• Monitor with `nvidia-smi` — watch memory usage under load, not just at startup

Key Takeaways

• Llama 2 70B FP16 = 140GB VRAM (70B params × 2 bytes)
• Add 20% overhead for KV cache, activations, and CUDA context
• H200 (141GB) fits FP16 on 1 GPU; H100 (80GB) needs FP8 or 2× GPUs
• FP8 is the sweet spot — 50% less VRAM with minimal quality loss
• INT4/GPTQ cuts to 35GB but quality degrades noticeably
• KV cache scales with context length × batch size — factor this into VRAM planning