Qwen 3.8 27B
Community sentiment from 10 posts · 400 comments · collected September 27, 2026 · generated September 27, 2026
Qwen 3.8 27B scores 68/100 overall in the r/LocalLLaMA community benchmark, collected September 27, 2026 from 10 posts and 400 comments. Its strongest category is Price / value at 85/100, and its weakest is Multimodal & vision at 50/100.
Confidence: medium — Large and highly engaged sample (10 posts, 400 comments) with many concrete numbers, but a substantial share of the discussion evaluates the Swift finetune, quants and tooling rather than the base model, and instruction following plus creative writing have no direct user data.
Category scores
Intelligence
72Users say the 27B 'can compete in some of the Benchmarks with API' and 'punches above its weight', and a 63-hour autonomous run never hallucinated an answer and repeatedly self-corrected; but even fans concede it is below SoTA frontier models, and the Swift finetune shows occasional accuracy loss ('It has accuracy loss when I test it').
Speed
78The Swift finetune delivers -58.3% thinking tokens and x1.95 speed with 190-475 tok/s decode and 7.4k-9.7k tok/s prefill reported on an RTX 5090; the base model does 50 tok/s at 100k context on a 16GB GPU, though end-to-end frontier models remain far faster for large projects.
Coding quality
68Strong coding stories: a Fable 2 PC recompilation done purely with the model, a hairy transaction bug fixed with a regression test, and daily-driver status for software dev and cybersec; offset by edit-retry issues, occasional junk files in projects, and landing 'within striking distance of Claude' rather than equal.
Instruction following
no dataNo data in the sample — comments discuss reasoning effort settings, loops and a finetune's IFEval drop, but contain no direct user assessments of base-model instruction following.
Long context
62Runs of 100k-262k context on consumer GPUs are celebrated, but needle-in-haystack tests show kvarn KV-cache recall around 75% vs 84% for f16, Q4 GGUFs reportedly break super long context tasks, and GPU-poor users are stuck at 80k-120k.
Price / value
85Local inference costs roughly 2.4 cents input / 70 cents output per 1M tokens with no API bills, a free research-purpose API exists, and adoption is huge: 100k+ downloads, #1 finetune and #9 model on HuggingFace trending.
Reliability & uptime
60A 63-hour autonomous run with self-correction and 'very rare' loops in vanilla Qwen impress, but default xhigh reasoning triggers endless 'but wait' loops, a 9-hour task melted down for 4 hours, and users report junk outputs in projects.
Creativity & writing
no dataNo data in the sample — style discussion concerns a Humanlike-Chat finetune, not base-model creative writing quality.
Multimodal & vision
50Native vision via mmproj is 'more than good enough for most visual comparison during coding sessions', but users report trouble debugging Vulkan graphics and prefer Gemma 4 for OCR.
Agentic & tool use
68Praised as the first local model users can 'turn away and let it do work without worrying', with harness skill files and multi-hour autonomous runs; held back by tool-call looping, edit retries and harness/template integration issues.
Summary
This benchmark is built from the 10 top r/LocalLLaMA posts mentioning Qwen 3.8 27B over the past month and 400 of their most upvoted comments. Much of the discussion orbits the Swift Qwen 3.8 27B efficiency finetune from UkisAI (-58.3% thinking tokens, x1.95 speed) and the community quant ecosystem around it, but the base model itself is reviewed extensively as the default local workhorse.
The community consensus is that Qwen 3.8 27B punches above its weight: users report complex refactors completed unsupervised, a hairy transaction bug fixed with a regression test, a Fable 2 PC recompilation done purely with the model, and a 63-hour autonomous Riemann-hypothesis run that never hallucinated an answer. With the Swift finetune plus DFlash2 speculation, decode reaches 190-475 tok/s on consumer GPUs, and 100k-262k contexts fit in 16GB VRAM with the right KV-cache setup.
The recurring complaints are about overthinking and reliability at default settings: the model defaults to xhigh reasoning and enters endless 'but wait' loops (one 9-hour task melted down for 4 hours), edits get retried over mangled indentation, quantized KV caches hurt long-context recall (75% vs 84% f16 on needle tests), vision trails Gemma 4 for debugging, and frontier APIs remain dramatically faster end-to-end (10 hours vs 30 minutes for a comparable project).
Overall the sample portrays a cheap, high-effort 27B that has become the default 'best thing I can run' for GPU-poor developers — exceptional autonomy and value, with speed and long-context recall as the main caveats. Confidence is medium: the sample is large and detailed, but a substantial share of comments evaluates the Swift finetune and tooling rather than the base model.
Pros and cons
Pros
- Exceptional agentic autonomy — users let it run unsupervised on complex refactors, bug fixes and multi-day autonomous runs without it abandoning the task
- Outstanding efficiency and speed with the Swift finetune: -58.3% thinking tokens, x1.95 speed and 190-475 tok/s decode with DFlash2 speculation on consumer GPUs
- Strong coding for the size class — real bugs fixed with regression tests, even a Fable 2 PC recompilation; some users run it as their only model for software dev and cybersec
- Runs very long contexts (100k-262k) on 16GB consumer GPUs with the right KV-cache configuration
- Essentially free local inference with native vision support and a huge community quant/finetune ecosystem (100k+ downloads, #1 finetune on HuggingFace)
Cons
- Chronic overthinking — default xhigh reasoning causes endless 'but wait' loops and multi-hour meltdowns unless reasoning effort is capped or the Swift finetune is used
- Slower than frontier models end-to-end — a project taking ~10 hours with Qwen is described as ~30 minutes of work with Claude
- Long-context recall degrades with quantized KV caches — kvarn needle-in-haystack scores around 75% vs 84% for f16
- Vision is usable for coding comparisons but struggles with graphics debugging and trails Gemma 4
- Edit and tool-use reliability is shaky — repeated edit retries over messed-up indentation and occasional junk files created in projects
Top quotes
“It is good, but only for "smaller" projects. I notice that its sometimes a lot of hustle ("but wait", "Now lets check again"..) and so on.”
caenum · 143 points negative view on Reddit ↗ “it's faster than any MoE I've used as well as good enough for me to use it as my only model for software dev, cybersec and IT adm”
tsangberg · 85 points positive view on Reddit ↗ “Qwen 3.8 27b xHigh really captured the essence of an autist with crippling paranoia having a panic attack.”
ILikeLegz · 86 points negative view on Reddit ↗ “once I capped reasoning tokens, the endless "but wait" loops disappeared and it landed within striking distance of Claude for routine coding tasks”
AIFrontierReads · 27 points positive view on Reddit ↗ “Qwen 3.8 27B really is the GOAT (so far) for local LLM's on my setup.”
joexner · 10 points positive view on Reddit ↗ “Unlike 3.8 Grug, this didn't make the model lazy - it just no longer seems to overthink on trivial tasks. It's still quite capable of long thinking when needed.”
Kodix · 55 points positive view on Reddit ↗ “it did it 45% faster, and complited it correctly, but missed some details that ideally it should report. It's faster for sure, but accuracy is definitely affected.”
ForeverSeeking69 · 54 points negative view on Reddit ↗ “Qwen is that kid in school who isn’t naturally intelligent but has a great work ethic and doesn’t give up.”
randylush · 22 points positive view on Reddit ↗ “Qwen 3.8 27b is way ahead of its predecessors and i also think that local ai will be the future, just because of privacy, and inference costs of frontier models”
caenum · 20 points positive view on Reddit ↗ “Across three 16K-output tests, Swift used **21.4% fewer tokens** and was **23% faster** overall.”
mmkaywhatevers · 10 points positive view on Reddit ↗ “i got to say qwen 3.8 has been amazing compared to others ive seen in its vram usage”
Himdo123 · 55 points neutral view on Reddit ↗ “Every quant even q2_1 outperformed every kvarn quant even kvarn8. Seems kvarn has trouble with recalling from the kv cache.”
Fancy-Snow7 · 12 points negative view on Reddit ↗
Top sample posts
Top 5 of 10 posts by score
- No, Engrams won't let you run 1T models locally. It does something even better. ↗
chocolateUI · 1312 points · 343 comments
- The Local LLM community feels like the golden era of the internet all over again ↗
feelspeaceman · 1170 points · 175 comments
- My RULE of Thumb of choosing a models ↗
Altruistic_Heat_9531 · 1088 points · 220 comments
- Thank you :) Swift Qwen 3.8 27B now has 100k+ downloads, is #1 finetune and #9 model on HuggingFace Trending ↗
Secure_Recording_472 · 987 points · 618 comments
- UkisAI Swift-Qwen3.8-27B / -58.3% thinking, x1.95 speed while keeping the accuracy of xhigh ↗
Secure_Recording_472 · 939 points · 398 comments
FAQ
- What is Qwen 3.8 27B's overall community score?
- 68 out of 100, with medium confidence: Large and highly engaged sample (10 posts, 400 comments) with many concrete numbers, but a substantial share of the discussion evaluates the Swift finetune, quants and tooling rather than the base model, and instruction following plus creative writing have no direct user data.
- How was the Qwen 3.8 27B benchmark collected?
- From 10 posts and 400 comments on r/LocalLLaMA sampled over the past month window.
- Which categories does the Qwen 3.8 27B report score?
- Intelligence, Speed, Coding quality, Instruction following, Long context, Price / value, Reliability & uptime, Creativity & writing, Multimodal & vision, Agentic & tool use.
- What are the main community pros and cons for Qwen 3.8 27B?
- Top pros: Exceptional agentic autonomy — users let it run unsupervised on complex refactors, bug fixes and multi-day autonomous runs without it abandoning the task; Outstanding efficiency and speed with the Swift finetune: -58.3% thinking tokens, x1.95 speed and 190-475 tok/s decode with DFlash2 speculation on consumer GPUs. Main cons: Chronic overthinking — default xhigh reasoning causes endless 'but wait' loops and multi-hour meltdowns unless reasoning effort is capped or the Swift finetune is used; Slower than frontier models end-to-end — a project taking ~10 hours with Qwen is described as ~30 minutes of work with Claude.
- When was the Qwen 3.8 27B data collected?
- Collected on September 27, 2026; the report was generated on September 27, 2026.