🦙Stalecollected in 81m

Test Qwen Models on llama.cpp Not Ollama

PostLinkedIn
🦙Read original on Reddit r/LocalLLaMA

💡Qwen issues? Blame Ollama—switch to llama.cpp for real results

⚡ 30-Second TL;DR

What Changed

Long CoT, tool calls, garbage outputs specific to Ollama/LMStudio

Why It Matters

Encourages switching runtimes, improving new model evaluations and reducing false negatives on capabilities.

What To Do Next

Deploy llama.cpp server to retest new Qwen models for accurate performance.

Who should care:Developers & AI Engineers

Key Points

  • Long CoT, tool calls, garbage outputs specific to Ollama/LMStudio
  • Ollama inferior to llama.cpp server for most use cases
  • LMStudio lacks presence penalty for new Qwen models
  • Parses tool calls wrongly in <thinking> tags

🧠 Deep Insight

Background and context from public sources — not the original article. 9 sources cited.

🔑 Enhanced Key Takeaways

  • Qwen3 models, including Qwen3-30B-A3B, achieve 342K token context length and 20–22 tokens/sec throughput on 80GB GPUs using llama.cpp's Vulkan backend[1].
  • Qwen3-Coder-Next requires specific flags like --tool-call-parser qwen3_coder and Q6_K quantization in llama.cpp or vLLM to resolve tool calling issues[2].
  • MLX on Mac has KV cache inconsistencies for Qwen3 during conversation branching, making llama.cpp the superior choice over MLX or optimized LM Studio[2][3].
  • Qwen3 supports 1M token context via hybrid attention (Gated DeltaNet + MoE) with near-linear compute scaling, natively handled by llama.cpp GGUF[4].
📊 Competitor Analysis▸ Show
Featurellama.cppOllamaLM StudiovLLMSGLang
Qwen3 Tool CallingFull support with custom parsersIssues in tagsLacks presence penaltyNative MoE/expert routingNative MoE/expert routing
Context LengthUp to 342K+ (Vulkan)Limited by runtime bugsHardware-dependent1M hybrid attentionHigh-throughput long context
QuantizationQ4_K_XL, Q5_K_M, Q6_KBasic GGUFOptimized MLX on MacServer-optimizedServer-optimized
Benchmarks (tokens/sec)20-22 on 80GB GPUInferior for most casesSlow on branching convosHigh for agentsHigh for agents
PricingFree/open-sourceFree/open-sourceFree (proprietary UI)Free/open-sourceFree/open-source

🛠️ Technical Deep Dive

  • Qwen3 uses hybrid attention alternating Gated DeltaNet (linear attention, 3:1 ratio with full attention) for 1M token contexts with near-linear scaling[4].
  • MoE architecture (e.g., Qwen3-235B-A22B) natively supported in llama.cpp via GGUF quantization (Q4_K_XL, Q5_K_M, Q6_K)[1][2][4].
  • Vulkan backend in llama.cpp optimizes Qwen3-30B-A3B inference speed/memory; ROCm/Vulkan enables AMD GPU support (e.g., Radeon 7900 XTX)[1][2].
  • Tool calling fixed with --tool-call-parser qwen3_coder, updated llama.cpp/vLLM, and recommended sampling parameters[2].

🔮 Future ImplicationsAI analysis grounded in cited sources

llama.cpp will dominate Qwen3 local inference by mid-2026
Ongoing GitHub discussions and benchmarks show rapid integration and superior performance over Ollama/MLX for new Qwen releases[2][6][8].
Qwen3 hybrid attention enables 1M+ context in open runtimes
Gated DeltaNet + MoE scales linearly, already supported in llama.cpp/vLLM, outperforming quadratic attention models[1][4].
Ollama/LMStudio lose share in agentic workflows
Persistent tool call and CoT bugs specific to these runtimes drive users to llama.cpp for Qwen3 coding/agent tasks[2].

Timeline

2025-01
llama.cpp community requests Qwen2.5-VL support on GitHub
2026-01
Qwen3 model family released with advanced CoT and tool calling capabilities
2026-02
Qwen3-Coder-Next launched by Alibaba Qwen team for local coding agents
📰

Weekly AI Recap

Read this week's curated digest of top AI events →

👉Related Updates

AI-curated news aggregator. All content rights belong to original publishers.
Original source: Reddit r/LocalLLaMA

This is a summary, not the original. Read the source, or get the weekly briefing.

Weekly AI briefing

One email a week. Unsubscribe anytime.