Gemma 3 270M on NVIDIA GeForce RTX 4070 SUPER
Can the NVIDIA GeForce RTX 4070 SUPER run Gemma 3 270M?
Yes, it runs well
Runs well. At F16 it needs about 1.8 GB of 12.0 GB usable, with an estimated speed of 538 tok/s.
- Best quant
F16- Generation speed
- 538 tok/s
- Prompt processing
- 94,667 tok/s
- First token (1K prompt)
- 0.3 s
- Largest safe context
- 32K
Download Gemma 3 270M
Recommended for the NVIDIA GeForce RTX 4070 SUPER: F16. Every other quantization has its own download link in the table below.
Quickest · Ollama
One command downloads a ready-to-run version and starts a chat.
ollama run gemma3:270m-it-fp16Quantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
Download the F16 file (opens in a new tab)
huggingface.co/unsloth/gemma-3-270m-it-GGUF (opens in a new tab)
ollama run hf.co/unsloth/gemma-3-270m-it-GGUF:F16Original weights · Hugging Face
Full-precision files from Google, for fine-tuning, vLLM, Transformers.
Official repo · GitHub
Reference code, inference scripts and docs from Google. The weights themselves download from Hugging Face.
github.com/google-deepmind/gemma (opens in a new tab)
git clone https://github.com/google-deepmind/gemmaHow the C grade is scored
Every result gets up to 100 points from four parts. The points decide the letter grade.
| Model quality | 2.7 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Memory use | 3.4 / 15 | |
| Total | 46.1 / 100 | 46 ptsUsable (C) · 46 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.4/15 |
Every quantization on the NVIDIA GeForce RTX 4070 SUPER
| Quant | Memory needed | Available | Speed | Fit | Grade · points | Download |
|---|---|---|---|---|---|---|
Q2_K | 1.3 GB | 12.0 GB | 3,763 tok/s | Runs well | 44 ptsUsable (C) · 44 of 100 points: Model quality 1.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.6/15 | GGUF (opens in a new tab) |
Q3_K_M | 1.4 GB | 12.0 GB | 2,962 tok/s | Runs well | 44 ptsUsable (C) · 44 of 100 points: Model quality 2.3/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.6/15 | GGUF (opens in a new tab) |
Q4_K_M | 1.4 GB | 12.0 GB | 2,291 tok/s | Runs well | 45 ptsUsable (C) · 45 of 100 points: Model quality 2.6/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.7/15 | GGUF (opens in a new tab) |
Q5_K_M | 1.4 GB | 12.0 GB | 1,893 tok/s | Runs well | 45 ptsUsable (C) · 45 of 100 points: Model quality 2.6/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.7/15 | GGUF (opens in a new tab) |
Q6_K | 1.5 GB | 12.0 GB | 1,590 tok/s | Runs well | 45 ptsUsable (C) · 45 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.8/15 | GGUF (opens in a new tab) |
Q8_0 | 1.5 GB | 12.0 GB | 1,166 tok/s | Runs well | 45 ptsUsable (C) · 45 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 2.9/15 | GGUF (opens in a new tab) |
F16 | 1.8 GB | 12.0 GB | 538 tok/s | Runs well | 46 ptsUsable (C) · 46 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.4/15 | GGUF (opens in a new tab) Original weights (opens in a new tab) |
Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.
Other hardware that runs it
- 47 ptsUsable (C) · 47 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.5/15 NVIDIA GeForce RTX 4060
- 47 ptsUsable (C) · 47 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.4/15 Apple M1 (16 GB)
- 47 ptsUsable (C) · 47 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 4.4/15 Apple M4 (16 GB)
- 46 ptsUsable (C) · 46 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.5/15 Apple M4 (24 GB)
- 46 ptsUsable (C) · 46 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.5/15 Apple M4 Pro (24 GB)
- 46 ptsUsable (C) · 46 of 100 points: Model quality 2.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 3.4/15 Intel Arc B580
Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.