Ornith-1.5-9B vs Qwen3-30B-A3B-Instruct-2507

Ornith-1.5-9B

A small coding and terminal-agent cousin with thinking on by default, XML tool calls that vLLM and SGLang parse, and 262,144 tokens of context. Ornith's own 4-bit builds run in under 8 GB in most local runtimes. The main risk is an absent publisher, with no licence file, no safety results, files replaced without a note and no replies.

Qwen3-30B-A3B-Instruct-2507

A quick general-purpose cousin, with 3.3B of 30.5B parameters active per token, for instruction following, tool calling and long documents without a thinking step. It needs about 21 to 23 GB at 4 bits, and several providers host it. The main risk is neglect, with no file changes in over a year, no answers from Alibaba and no safety results.

Ornith-1.5-9B

1. Start it with ollama run ornith-1.5:9b, or llama-server -hf ornith-ai/Ornith-1.5-9B-GGUF with the Q4_K_M file
2. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
5. Use temperature 0.6, top_p 0.95, top_k 20 for coding and temperature 1.0 with presence_penalty 1.5 for general tasks, per the card
6. Pin a revision when you download, since Ornith has replaced files in place, and add mmproj-Ornith-1.5-9B-BF16.gguf (0.9 GB) for image input in llama.cpp
7. Validate JSON output yourself, since structured output isn't documented

Qwen3-30B-A3B-Instruct-2507

1. Quickest start is ollama run qwen3:30b-instruct, 19 GB. Plain qwen3:30b and qwen3:30b-a3b are the Thinking-2507 edition, not this one
2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-30B-A3B-Instruct-2507 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser hermes, 61 GB of weights fits the GPU share
3. Use the hermes parser in vLLM or qwen25 in SGLang, the template emits JSON inside tool_call tags
4. Don't pass enable_thinking, this edition never thinks and the card says the flag isn't needed
5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and min_p 0, with presence_penalty up to 2 against repetition
6. Leave config.json as it is unless you need more than 262,144 tokens, the 1M mode swaps in config_1m.json and runs one sequence at a time
7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented