Gemma 4 E4B on Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB)

Can the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB) run Gemma 4 E4B?

Barely: it runs very slowly (tight fit)

Very slow (tight fit). At Q3_K_M it needs about 5.1 GB of 5.2 GB usable, with an estimated speed of 1.5 tok/s.

Best quant: Q3_K_M
Generation speed: 1.5 tok/s
Prompt processing: 1.3 tok/s
First token (1K prompt): 768.0 s
Largest safe context: 15K

Best app to run it on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB)

On Linux

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

One command with Ollama’s own build of this model.
Serves an OpenAI-compatible API that other apps and coding tools can use.

ollama run gemma4:e4b

llama.cpp Usually the first to support new model architectures.
KoboldCpp

How we choose: the files published for this model, which apps run in a container on a NAS without a graphics card (models run on its processor), and whether the model fits fully in the memory models can use. Details.

Download Gemma 4 E4B

Recommended for the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB): Q3_K_M. 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.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run gemma4:e4b

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q3_K_M file (opens in a new tab)

huggingface.co/unsloth/gemma-4-E4B-it-GGUF (opens in a new tab)

ollama run hf.co/unsloth/gemma-4-E4B-it-GGUF:Q3_K_M

Original weights · Hugging Face

Full-precision files from Google, for fine-tuning, vLLM, Transformers.

huggingface.co/google/gemma-4-E4B-it (opens in a new tab)

No sign-in needed.

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)

Google DeepMind’s official Gemma library.

git clone https://github.com/google-deepmind/gemma

Links checked 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 57Good quality (B) · 57 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q3_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Very slowtight fit: How well it runs on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	25.7 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.	24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	2.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	67.6 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (8 GB)

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	4.4 GB	5.2 GB	1.9 tok/s	Very slow	47Fair quality (C) · 47 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (UD-Q2_K_XL) (opens in a new tab)
`Q3_K_M`	5.1 GB	5.2 GB	1.5 tok/s	Very slowtight fit	57Good quality (B) · 57 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	6.0 GB	5.2 GB	1.0 tok/s	Very slowfar over memory limit	64Good quality (B) · 64 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 50/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	6.8 GB	5.2 GB	—	Won't run	65Good quality (B) · 65 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	7.7 GB	5.2 GB	—	Won't run	67Good quality (B) · 67 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	9.6 GB	5.2 GB	—	Won't run	68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	17.2 GB	5.2 GB	—	Won't run	68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking.	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

68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX F16 · 52.9 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. Intel Arc B580 Q8_0 · 48.4 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3060 12GB Q8_0 · 50.0 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 3090 F16 · 59.9 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER Q8_0 · 70.0 tok/s · Runs great
68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 85/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4090 F16 · 64.5 tok/s · Runs great

Quick answers

How much memory does Gemma 4 E4B need on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 8GB?

At Q3_K_M it needs about 5.1 GB. The Intel Celeron J3455 / N3450 (Apollo Lake) NAS 8GB has 5.2 GB usable.

How fast is Gemma 4 E4B on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 8GB?

About 1.5 tok/s at Q3_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Gemma 4 E4B should I use on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 8GB?

Q3_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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.