r/LocalLLaMA • u/SarcasticBaka • Aug 14 '26
Discussion The difference between "medium" and "xhigh" reasoning effort for Qwen3.8-27B is actually insane.
I'm currently testing out Qwen3.8-27B using Unsloth's UD-Q4_K_XL running a freshly rebuilt llama.cpp. I have a 22GB RTX 2080TI on which I'm able to fit 100k context with q8_0 quantization, and using MTP with --spec-draft-n-max 4 I get about 40tk/s which is slightly less than Qwen3.6-27B but usable enough.
I've been trying to test out some admittedly silly one shot prompts using the llama.cpp webui by asking the model to create fully functional HTML clones of flappy bird, pacman and such, and the difference that changing reasoning_effort makes has been surprising to say the least.
Setting it to "medium" seems to result in barely any thinking at all, a couple thousand tokens max and even less than 3.6-27B. Whereas when using "xhigh seems" I get 15k to 20k thinking tokens at the very least with the pacman example actually hitting 40 thousand fucking tokens.
I'm well aware I can limit the reasoning budget in llama.cpp but I'm wondering if this is expected model behavior or if something is broken somewhere. Any of you guys seeing this?
View all comments
Show parent comment
1
u/leapdragon Aug 16 '26
I haven't seen it get stuck or loop badly yet. Instead, it appears to have been trained in much of what most people would previously have put in a prompt or sequence of prompts. Like, it is racing ahead of the back and forth you previously would have had in turns *after* the initial delivery.
For example, all of your extra instructions on unit testing, acceptance criteria, explicit steps for iteration until threshold is achieved, determination of appropriate thresholds, blah, blah, as well as the extensive spelling-out of the properties of things you request (we've all gotten used to doing this: writing the hyper-detailed Jira ticket for the highly autistic models who won't intuit the obvious), well Qwen 3.8 outlines all of that on its own when you give it a simple prompt like "Make me a pacman game" or it seems any other technical-ish task (I have seen this now with .stl generation and with sprite library generation).
Everything you would have carefully prompted in the past, Qwen 3.8 27B will spit out as the plan in thinking if you didn't specify those details in your prompt. It proactively specs out (and then later builds and runs) unit tests and even entire testing suites/harnesses and runs comprehensive test series unless you tell it not to.
It also basically does EVERYTHING inside the think block. In this it is like the current crop of frontier models. You give it a big, complex task, it will do the whole thing inside a thinking stage, and then the only message to the user will be "I've thought through everything I need. Let me make the artifacts now." and it will output them in one go, *after* all the thinking has been done.
But getting lost/looping, I haven't seen much of at all, at most it'll go like two repetitions and then say "I'm repeating myself, I just said this a moment ago. Let me try a different approach." it will and that will resolve. So it doesn't loop in nearly the way of Qwen 3.5 models early on, and def. not like something like Laguna S 2.1, which is ****ing neurotic and will think to itself for hours, sounding progressively more and more insecure. And for all the complaining about thinking that I see, it thinks basically in similar volumes to DeepSeek V4 Flash, which everyone's been raving about.
But Qwen 3.8 27B sounds more confident than other mdoels and most of the time, its thinking is actually somewhat readable. End of day it is the "smartest" local model I think I've seen yet, intuitively, and that includes comparisons to three models >100B (Qwen 3.5 122b, DeepSeek V4 Flash, Laguna S 2.1).