TextDense27B params8K max context

Gemma 2 27B VRAM Requirements: How Many GPUs & What It Costs

Gemma 2 27B needs 27.0 GB of VRAM for its weights at FP8 (E4M3) — 28.5 GB once a KV cache is loaded. Below is the full breakdown: which GPUs fit, how many you need, what it serves, and what it costs per million tokens. Every figure comes from tokcalc's open-source capacity model.

Weights (FP8 (E4M3))
27.0 GB
28.5 GB with KV cache
Fits on 1 GPU?
Yes
Mac M3 Max (64GB) or larger
Cheapest config
$0.0248
8× RTX 3080 10GB / 1M tokens
Fastest config
29467
tok/s on 2× Cerebras CS-3 (WSE-3)
VRAM requirement by quantization
Weight footprint = params × bytes per param. The “with KV cache” column adds one request at 4K context.
QuantizationWeightsWith KV cacheSmallest single GPU
FP1654.0 GB55.5 GBMac M3 Max (64GB) (64 GB)
FP8 (E4M3)recommended27.0 GB28.5 GBV100 SXM2 32GB (32 GB)
AWQ 4-bit14.9 GB16.4 GBA10G 24GB (24 GB)
Which GPU should you use?
Reference workload: 8K context, 8 concurrent users, continuous batching, FP8 (E4M3). Ranked by fitting first, then by tokens per dollar-hour.
GPUGPUsTotal VRAMDecode tok/sAggregate tok/sCost / 1M tokens
RTX 3080 10GB8×80 GB186.617916$0.0248
RTX 3090 24GB4×96 GB114.95274$0.0527
RTX 4090 24GB4×96 GB123.85940$0.0748
RTX 4080 16GB4×64 GB88.034226$0.0789
RTX 5090 32GB2×64 GB110.02640$0.1052
A10G 24GB4×96 GB73.673536$0.1131
RTX A4000 16GB4×64 GB55.002640$0.1263
T4 16GB4×64 GB39.291200$0.1852
V100 SXM2 32GB2×64 GB55.251326$0.2095
A100 40GB SXM42×80 GB95.152284$0.2189
L4 24GB4×96 GB36.831768$0.2514
AMD MI300X 192GB1×192 GB191.42297$0.3024

RTX 3080 10GB has no NVLink, so 8-way tensor parallelism runs over PCIe. tokcalc applies a flat 0.85× multi-GPU efficiency factor for this, which is realistic for NVLink-equipped datacenter cards but optimistic for PCIe scale-out — treat the throughput and cost figures for this configuration as an upper bound, and measure before committing.

How concurrency changes with context length
On 8× RTX 3080 10GB at FP8 (E4M3). KV cache scales linearly with context, so long contexts cut the number of users you can serve from the same GPUs.
ContextConcurrent usersKV per requestFits?
4K341.54 GB✓ fits
8K173.09 GB✓ fits
33K412.35 GB✓ fits
66K224.70 GB✓ fits
131K149.39 GB✓ fits
Frequently asked questions

Can Gemma 2 27B run on a single GPU?

Yes. At FP8 (E4M3) the model needs 28.5 GB of VRAM, so it fits on a single Mac M3 Max (64GB) or anything with more VRAM. At full FP16 it needs 55.5 GB, which fits on one Mac M3 Max (64GB) or larger.

How many GPUs does Gemma 2 27B need?

At FP8 (E4M3) with 8,192-token context and 8 concurrent users, the cheapest configuration that fits is 8× RTX 3080 10GB (80 GB total VRAM). $0.0248 per 1M output tokens.

How fast can Gemma 2 27B be served?

On 2× Cerebras CS-3 (WSE-3) at FP8 (E4M3), the aggregate throughput is 29467 tokens/sec with continuous batching. That hardware has no published rental price, so its cost per million tokens is not comparable.

How much VRAM does Gemma 2 27B need?

Weights alone: 54.0 GB at FP16, 27.0 GB at FP8 (E4M3). Add KV cache for your context length and concurrency — every concurrent request at 8,192 tokens costs extra VRAM, so budget headroom above the weight figure.

Should I run Gemma 2 27B in FP8 or FP16?

FP8 halves the weight footprint (54 GB → 27 GB) and is faster than FP16 on Hopper and Blackwell, where it has native kernels. FP16 remains the reference quality bar; FP8 loses a small amount of accuracy in exchange for roughly doubling the batch size you can serve per GPU.

Is it cheaper to self-host Gemma 2 27B than to call an API?

At 8× RTX 3080 10GB the marginal cost is $0.0248 per 1M output tokens, before you add idle capacity, ops staff, or egress. That is typically cheaper than frontier API pricing at sustained volume, but API calls win when your load is bursty or too small to keep a GPU busy. The Build vs Buy tab on tokcalc prices this against a specific provider for you.

Try Gemma 2 27B with your own context and concurrency

The calculator uses the exact same formulas as this page — change the workload and watch every number update.

Open in calculator
Model architecture
The numbers behind the KV-cache and throughput math.
Total parameters27.00B
Active parameters per token27.00B
ArchitectureDense
Attention layoutFull attention (GQA)
Transformer layers46
Hidden dimension4608
Attention heads32 query / 16 KV (GQA)
Head dimension128
Vocabulary size256,000
Max context (catalog)8K
KV cache per token @ 8K368.0 KB

Every layer caches keys and values for the whole context, so the KV cache grows linearly with conversation length.