Infrastructure Tools

LLM GPU Calculator

How many GPUs do you need to run a model at your tokens per second target? Pick a model, a precision and a traffic profile, prefill and prompt caching included, to see which datacenter GPUs fit and how many of each you need.

Start from a model instead

Llama 3.3 70B Instruct

Meta Native BF16 Hardware requirements page
Weights at BF16
141 GB
Active parameters
70.6B
dense model
KV cache per token
320 KB
KV cache per stream
10.7 GB
at 32,768 tokens
Memory needed
485 GB
32 concurrent streams
Time to first token
334 ms
16,128 of 32,256 prompt tokens prefilled

The Meta repo is gated; geometry read from the unsloth mirror, which ships the same config.

GPUs for 1,000 tokens/s 68 of 105 parts fit at these settings

Roofline estimates. Figures marked ~ use a derived tensor-core rate.

GPUMemoryTotal GPUs
432 GB 4 Specs
288 GB 4 Specs
TPU 8t Announced
216 GB 8 Specs
TPU 8i Announced
288 GB 6 Specs
288 GB 6 Rent
288 GB 6 Rent
186 GB 8 Rent
288 GB 8 Rent
192 GB 8 Specs
432 GB 6 Specs
262.5 GB 8 Rent
180 GB 8 Rent
Huawei logo
Ascend 970 Announced
288 GB 6 Specs
192 GB 8 Specs
OpenAI logo
JalapeƱo Announced
216 GB 8 Specs
256 GB 10 Rent
192 GB 12 Rent
64 GB 24 Specs
Huawei logo
Ascend 960 Announced
288 GB 12 Specs
141 GB 16 Rent
80 GB 16 Rent
32 GB
128 GB 20 Specs
141 GB 16 Rent
94 GB 24 Rent
128 GB 20 Specs
80 GB 24 Rent
80 GB 24 Specs
144 GB 24 Specs
96 GB 32 Rent
128 GB 32 Specs
80 GB 40 Specs
96 GB 40 Rent
128 GB 12 Specs
95 GB 32 Specs
96 GB 40 Rent
128 GB 60 Specs
96 GB 32 Specs
112 GB 40 Specs
48 GB 48 Specs
32 GB
64 GB 40 Specs
128 GB 32 Specs
48 GB 64 Rent
128 GB 32 Specs
L40S 48GB 2 nodes
48 GB 64 Rent
80 GB 48 Specs
80 GB 40 Specs
80 GB 48 Rent
80 GB 40 Rent
40 GB 64 Specs
40 GB 64 Rent
24 GB
48 GB 64 Specs
32 GB
32 GB
48 GB 64 Rent
72 GB 56 Specs
32 GB
32 GB
32 GB
32 GB
32 GB
32 GB
32 GB
L40 48GB 2 nodes
48 GB 96 Rent
64 GB 64 Specs
24 GB
24 GB
24 GB
48 GB 112 Rent
A40 48GB 2 nodes
48 GB 112 Rent
141 GB 64 Specs
96 GB 72 Specs
24 GB
32 GB
48 GB 144 Specs
96 GB 128 Specs
24 GB
24 GB
32 GB
64 GB 96 Specs
24 GB
48 GB 112 Specs
48 GB 112 Specs
24 GB
24 GB
L20 48GB 2 nodes
48 GB 128 Specs
32 GB
32 GB
24 GB
24 GB
24 GB
Cambricon logo
MLU370-X8 2 nodes
48 GB 160 Specs
48 GB 144 Specs
32 GB
24 GB
24 GB
48 GB 288 Specs
24 GB
24 GB
24 GB
32 GB
24 GB
28 GB

How this is calculated

  • Weights are parameters times bytes per parameter: 2 at BF16, 1 at FP8, 0.5625 at INT4 or FP4 including block scales. The figure is the full checkpoint, not the active subset.
  • KV cache follows the model's config.json: layers times KV heads times head dimension, K and V, in 16-bit. Sliding-window layers are charged for the window only, MLA models for their latent, and linear-attention layers for a fixed state per stream.
  • A GPU offers 90 percent of its memory to weights and cache, less 1 GB of workspace. Tensor parallel widens across 1, 2, 4, 8 and 16 GPUs until the pool fits.
  • Prefill is compute-bound: two FLOPs per active parameter for every prompt token the prefix cache does not already hold, at 60 percent of the dense tensor peak. Prompt tokens are the context less the output per request; the cache hit rate is the share of them served from an earlier request (system prompts, shared documents, chat history). The attention term that grows with the square of the prompt is not counted, so very long prompts cost a little more than shown.
  • Decode is bandwidth-bound: every step streams the weights the batch touches and every stream's cache at 75 percent of peak bandwidth, with a compute floor at 60 percent of the dense tensor peak. For a mixture of experts the weights touched grow with concurrency: a batch of n streams choosing k of E experts lands on E(1 - (1 - k/E)^n) distinct experts, so DeepSeek-class models at 32 streams read most of the expert pool, not the active parameters. FP8 weights compute at FP8 where the part has it; 4-bit weights compute at 16-bit unless the part has FP4 tensor cores.
  • A request costs its prefill plus its output tokens' share of the decode steps it sits in, so a replica's rate is output tokens over that GPU time; "prefill" in the table marks parts where prefill is more than half of it. Time to first token is the prefill of one request on the fastest fitting part. Replicas are the target rate divided by one replica's rate, rounded up. Total GPUs is replicas times the tensor-parallel width. Tensor parallel is the only split modelled; expert parallel and disaggregated prefill can do better. Measured throughput from a tuned serving stack can beat these numbers; they are a planning floor, not a benchmark.

Ā© 2026 Flopper.io - Compare the GPUs Powering AI