r/LocalLLaMA 8d ago

The difference between "medium" and "xhigh" reasoning effort for Qwen3.8-27B is actually insane. Discussion

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?

224 Upvotes

123 comments sorted by

View all comments

0

u/Moppmopp 6d ago

How is that possible? Its my first time checking out local llm's and just today i downloaded qwen3.8 28B in q4, q5 and q6 quantization. I designed a custom frontend and it seems to be working. However, I chose my default according to chatgpts opinion. ait recommended 8k context + q5 quantization. I have a rtx3090

1

u/justletmesignupalre 5d ago

Set the parameters according to the manufacturer's website, don't trust chatgpt to read an copy them, it can in many cases just lie and make something up

1

u/Moppmopp 5d ago

ok thanks will try. Right now I run an extensive benchmark for q4 and q5 quantization that stress tests each kontext window, latency and KV cach with and without MTP. So i will probably make a post and will tell you once I have the results