DiffusionGemma 26B A4B IT vs NVIDIA Nemotron 3.5 Bolt E4B 4GB

DiffusionGemma 26B A4B IT

A fast local generation cousin for low-concurrency work on text, images and video, with optional thinking and Gemma 4's tool format, under Apache 2.0. It needs about 62 GB for Google's BF16 files and runs only in Transformers or SGLang. The main risk is quality, since Google's own figures put it below Gemma 4 26B A4B, and it's labelled experimental.

NVIDIA Nemotron 3.5 Bolt E4B 4GB

A small cousin for voice and device assistants, game characters and robot interfaces, trained for multi-turn tool calls, instruction hierarchy and short spoken replies, with thinking switchable per request. NVIDIA's Q4_K_M GGUF needs about 8 GB, and Ollama and LM Studio carry it. Context is 64K, half the Gemma 4 base, and NVIDIA publishes no safety results.

DiffusionGemma 26B A4B IT

1. Serve it with sglang serve --model-path google/diffusiongemma-26B-A4B-it --dllm-algorithm Gemma4Renoise --trust-remote-code on SGLang v0.5.22 or later, then call /v1/chat/completions
2. In Transformers, install transformers>=5.11.0 and load DiffusionGemmaForBlockDiffusion with dtype="auto"; generation_config.json already holds the recommended sampler
3. Turn thinking on with enable_thinking=True in apply_chat_template or <|think|> at the start of the system prompt, read the reasoning between <|channel>thought and <channel|>, and drop it from history before the next turn
4. Don't rely on temperature, top_p, logit_bias or JSON Schema in SGLang, which ignores or rejects them for this model; validate JSON yourself
5. Streaming arrives one 256-token canvas at a time, not token by token
6. Put images before text in the prompt, and pick an image token budget of 70 to 1,120 by how much detail the task needs

NVIDIA Nemotron 3.5 Bolt E4B 4GB

1. Quickest start is ollama run nemotron-3.5-bolt:e4b, about 8 GB of files, and set num_ctx to 65536 or less, since NVIDIA supports 64K
2. With NVIDIA's GGUF use llama-server -m Nemotron-3.5-Bolt-E4B-Q4_K_M.gguf -c 65536 -ngl 999 --jinja, and add --reasoning on --reasoning-budget <tokens> to cap thinking
3. With vLLM 0.31.0 or later pass --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4 and the repository's chat_template.jinja
4. Pass enable_thinking explicitly in chat_template_kwargs, since the template defaults to off whatever the card says, and set skip_special_tokens false as the card's examples do
5. Use temperature=1.0 and top_p=0.95 in both modes, as the card says
6. Set conversational_mode true for spoken replies, which appends a brevity instruction to the system prompt
7. Answer a slow tool at once with a pending tool message, then send the result later as a user message starting TOOL RESULT, as the card's asynchronous pattern says
8. Keep persistent rules in the system prompt and send state updates as separate user or system messages in order, per the card's prompting guidelines