@mtasic85: You know I am going down the rabbit hole, when you see me making LFM2.5 2.6B behaving close to Qwen3.8 27B when it come…
Summary
@mtasic85 demonstrates that with prompt programming alone, without fine-tuning, LFM2.5 2.6B can behave close to Qwen3.8 27B in tool calling and skill system applications.
View Cached Full Text
Cached at: 08/20/26, 06:58 AM
You know I am going down the rabbit hole, when you see me making LFM2.5 2.6B behaving close to Qwen3.8 27B when it comes to tool calling and using skill system - all prompt programming, zero fine-tuning. https://t.co/QQATTb3gYA
Similar Articles
Qwen-3.6-27B, llamacpp, speculative decoding - appreciation post
Reddit user demonstrates llamacpp speculative decoding boosting Qwen-3.6-27B token speed from 13.6 to 136.75 t/s, sharing exact commands and hardware setup.
Qwen3.8 27B C8 at 972 TG / 5,680 PP on 4x MI100 rig ($6.5k) using my new INT8 vLLM fork
A new vLLM fork introduces comprehensive INT8 optimization for Qwen3.8 27B on older AMD MI100 GPUs, achieving up to 972 tokens per second throughput with rigorous accuracy validation.
@noctus91: I recently switched from Qwen 3.5 9B to LFM2.5-8B-A1B by @liquidai, and it's quickly become my default local model in H…
A user shares their positive experience switching from Qwen 3.5 9B to Liquid AI's new LFM2.5-8B-A1B model, praising its speed and reliability for agentic tasks while noting coding remains a weakness. The model is an 8B MoE with 1.5B active parameters and 128K context, optimized for devices and server-side use.
LFM 2.6B is a lot of fun.
The author shares hands-on experience with LFM 2.6B, a small model designed for phones, praising its speed and usefulness for quick tasks like summarization and autocomplete, though it has a 128k context limit.
Qwen3.6 27B more dumb in vLLM compared to llama.cpp
A user reports that the Qwen3.6-27B model performs better and more reliably with llama.cpp than with vLLM, citing tool call errors and 'lobotomized' behavior in vLLM despite extensive configuration.