DiffusionGemma 26B A4B IT vs Laguna XS 2.1

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.

Laguna XS 2.1

A small coding and agent cousin with 3B active parameters, so it's quick on modest hardware. Poolside's 4-bit GGUF, also Ollama's default, needs about 24 GB, and every major runtime runs it. The main risks are that nobody at Poolside answers its discussions, there are no safety results, and the SGLang route runs repository code.

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

Laguna XS 2.1

1. Quickest start is ollama run laguna-xs-2.1, 20 GB of files, the same Q4_K_M as Poolside's GGUF
2. On our reference machine use llama-server -hf poolside/Laguna-XS-2.1-GGUF:Q4_K_M --jinja -c 131072, from a llama.cpp release with the laguna architecture (b11772 has it), or BF16 with vLLM (66.9 GB)
3. With vLLM use --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on a build with vllm-project/vllm#47311, or --tool-call-parser glm47 on older builds
4. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
5. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
6. Sampling per the card is temperature 1.0 and top_k 20
7. The card warns that Ollama on Apple Silicon may return empty output until llama.cpp#25389 ships
8. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented