Gemma · 27.4B parameters
Gemma 3 27B: GPU memory requirements and which GPU to rent
Google's Gemma 3 27B uses a 1,024-token sliding window on five layers in six, so its KV cache grows far more slowly with context than a classic dense model's.
- Weights at FP827 GB55 GB at 16-bit · 15 GB at 4-bit
- FP8, 8k context, 1 sequence31 GBweights + KV cache + runtime
- Suggested here1× L40S$429 a month · dedicated
Inference
How much GPU memory Gemma 3 27B 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 precision | Weights | 4k context | 32k context | 128k context | 8k × 16 sequences | Suggested here, 8k |
|---|---|---|---|---|---|---|
| 16-bit (BF16 / FP16) | 55 GB | 59 GB | 62 GB | 70 GB | 76 GB | 1× A100 · $649/mo |
| 8-bit (FP8 / INT8) | 27 GB | 31 GB | 33 GB | 41 GB | 48 GB | 1× L40S · $429/mo |
| 4-bit (GPTQ, AWQ, Q4) | 15 GB | 18 GB | 20 GB | 28 GB | 35 GB | 1× L4 · $169/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. Five layers in six use a 1,024-token sliding window.
Hardware
GPU servers that run Gemma 3 27B
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 Gemma 3 27B
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.
| Method | Memory | Suggested here |
|---|---|---|
| QLoRA, 4-bit base | 29 GB | 1× RTX 5090 · $279/mo |
| LoRA, 16-bit base | 71 GB | 1× A100 · $649/mo |
| Full fine-tune, mixed precision | 453 GB | 2× B300 · $7,580/mo |
Architecture at a glance
Five layers in six use a 1,024-token sliding window. Figures from the model's published configuration; method on the calculator page.
Gemma 3 27B hardware: questions answered
How much VRAM does Gemma 3 27B need?
For the weights alone: about 55 GB at 16-bit, 27 GB at FP8 and 15 GB at 4-bit. Serving it at FP8 with an 8k-token context and one sequence takes about 31 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.52 GB per 1,000 tokens at 16-bit.
Can Gemma 3 27B run on a single GPU?
Yes, at FP8 with a moderate context: one NVIDIA L40S (48 GB GDDR6) holds it, for $429 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 Gemma 3 27B?
For FP8 inference with an 8k context and one sequence, the configuration we would suggest is 1× L40S · $429/mo; at 4-bit, 1× L4 · $169/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 Gemma 3 27B?
With a 2k-token sequence and a micro-batch of 4: about 29 GB for QLoRA on a 4-bit base, 71 GB for LoRA on a 16-bit base, and 453 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 Gemma 3 27B on 1× L40S for $429 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.