Gemma 4 E2B IT vs Nemotron 3 Nano 30B A3B

Gemma 4 E2B IT

A small cousin for light agent work, tool-calling loops, transcription and image reading on a phone or laptop, under Apache 2.0. Google's 4-bit build needs about 5 GB with working space and runs in all the common runtimes. Google's card puts it far below larger Gemma 4 sizes on agent and coding tasks, with no published safety results.

Nemotron 3 Nano 30B A3B

A fast hybrid Mamba-Transformer cousin with 3.5B active parameters for reasoning and tool calling over very long inputs, in every major local runtime. A 4-bit build needs about 22 to 23 GB. The main risks are that NVIDIA's documented vLLM path runs repository code, no safety results are published and NVIDIA hasn't answered reports since March.

Gemma 4 E2B IT

1. On the reference machine run llama-server -hf google/gemma-4-E2B-it-qat-q4_0-gguf --hf-file gemma-4-E2B_q4_0-it.gguf --jinja -c 131072, and add --mmproj with gemma-4-E2B-it-mmproj.gguf for images and audio
2. With Ollama run ollama run gemma4:e2b and raise num_ctx or OLLAMA_CONTEXT_LENGTH, since the default context is small and agents want at least 64K
3. In vLLM or SGLang pass --tool-call-parser gemma4 --reasoning-parser gemma4 (vLLM also --enable-auto-tool-choice), or tool calls come back as text; Google's w4a16 build is the 4-bit route there
4. Thinking is off by default; pass enable_thinking=True or start the system prompt with <|think|>, and drop earlier turns' thinking from history except on tool-call turns
5. Put images before the text and audio after it, keep audio to 30 seconds and video to 60 frames, and validate tool names and arguments before running them

Nemotron 3 Nano 30B A3B

1. Start it with ollama run nemotron-3-nano:30b (18 GB MLX on a Mac, 24 GB q4_K_M elsewhere)
2. On the reference machine use BF16 with vLLM, after wget https://huggingface.co/nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16/resolve/main/nano_v3_reasoning_parser.py, then vllm serve nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 --max-model-len 262144 --trust-remote-code --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser-plugin nano_v3_reasoning_parser.py --reasoning-parser nano_v3
3. NVFP4 needs an NVIDIA Blackwell GPU, and FP8 isn't documented on gfx1151
4. Without the qwen3_coder tool parser and the nano_v3 reasoning parser, tool calls and reasoning come back as plain text
5. Card sampling is temperature 0.6 and top_p 0.95 for tool calling, temperature 1.0 and top_p 1.0 for reasoning
6. Thinking is on by default, so pass enable_thinking as false in chat_template_kwargs for short tasks
7. Set VLLM_ALLOW_LONG_MAX_MODEL_LEN=1 and raise --max-model-len only when you need more than 262,144 tokens
8. In SGLang the main branch names the reasoning parser nemotron_3, not the card's nano_v3
9. Filter untrusted tool results before they reach the model, as NVIDIA warns prompt injection can lead to code execution
10. Validate JSON output yourself or use the runtime's guided decoding, since none is documented for the model