NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Qwen3.8-27B

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.

Qwen3.8-27B

A dense cousin for coding and agent work with image and video input that runs almost anywhere. Ollama's 4-bit build needs about 22 GB, and five providers host it for agents without the hardware. The main risk is that nobody at Alibaba answers, there are no safety results or agent guidance, and the tool format is only in the template.

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

Qwen3.8-27B

1. Quickest start is ollama run qwen3.8, about 18 GB of files
2. On our reference machine use BF16 with vllm serve Qwen/Qwen3.8-27B --max-model-len 131072 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder, since FP8 on gfx1151 isn't documented
3. Use the qwen3_coder tool parser, SGLang's cookbook says the Hermes parser leaves its calls unparsed
4. Thinking is on by default, pass chat_template_kwargs with enable_thinking false for short tasks, and read the reasoning from reasoning_content
5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
6. Sampling per the card is temperature 1.0 and top_p 0.95 when thinking, temperature 0.7, top_p 0.8 and presence_penalty 1.5 without
7. Preserved thinking keeps earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
8. Turn on YaRN only beyond 262,144 tokens, the card warns static YaRN can cost quality on short texts
9. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented