Will It Fit?
Estimate text inference VRAM across Transformers and vLLM with a compact, explainable breakdown.
Model pages and release notes are included here too.
Gemma 2 27B · vLLM · Official BF16 checkpoint
Required GPU VRAM (0.9 budget)
68.1 GB
Core estimate: 61.3 GB. Against RTX 4090 24GB, this leaves 42.4 GB of deficit.
At 4,096 tokens, the estimated max concurrency is 0 concurrent requests.
Quick read
Selected GPU
Runtime
Load dtype
GPU utilization
GPU count
KV cache dtype
Context length
Current concurrency
Max concurrency @ context
Class
Bandwidth
Nominal VRAM
Core estimate
Required GPU VRAM (0.9 budget)
Deficit
GPU compare
What fits this setup
Breakdown
Where the memory goes
Weights
27B resident parameters at 2.00 bytes each. Calibrated from the official checkpoint profile.
54.0 GB
KV cache
Concurrency 1, context 4,096, 46 KV-bearing layers, 16 KV heads, BF16 cache storage.
1.7 GB
Runtime / safety overhead
Conservative buffer for allocator fragmentation, kernels, and runtime scratch space.
5.6 GB
Weights = parameter count × bytes per parameter.
KV cache grows with context length, KV-bearing layers, concurrent requests, and the selected KV cache dtype.
Show the substituted formulas
Weights
parameter count × bytes per weight
27B × 2.00 = 54.0 GB
Google's official Gemma 2 27B Instruct release is exported in bfloat16.
KV cache
batch × effective KV tokens across attention layers × 2 × KV heads × head dim × bytes per KV element
1 × 188,416 × 2 × 16 × 144 × 2 = 1.7 GB
Longer context, deeper models, and larger batches all expand the cache linearly. BF16 controls the bytes per stored KV element.
Overhead
max(1.5 GB, 10% of weights + KV cache + linear state)
max(1.5 GB, 10% of 55.7 GB) = 5.6 GB
This leaves room for runtime buffers instead of claiming an unrealistically exact fit.
Model
Selected model
Gemma 2 27B
27B dense • 8,192 context • 16 KV heads
Total params
Active params
Layers
Hidden size
Attention heads
KV heads
KV-bearing layers