logoalt Hacker News

wronglebowskitoday at 10:52 AM3 repliesview on HN

It’s really interesting timing, Qwen over thinking is what kills it for me. I’m just glad we have more options in this size class now.


Replies

jermaustin1today at 2:23 PM

I've been using Qwen3.6 35B A3B, and with reasoning turned on, I'd say 2/3 (give or take) of the tokens for a response are thinking tokens. Which at 70+ tps locally, that isn't that awful. I run an 80k context across 4-10 "agents" for my solo TTRPG, where Qwen is the GM, each NPC at a location, the director, and the narrator.

Each turn is about 45-60 seconds to generate all of the various responses. The GM and director have reasoning on, and the NPCs/Location/Narrator do not.

It's a fairly good "engine" for that. I'm not sure how a denser Qwen would do here regarding speed.

show 1 reply
ComputerGurutoday at 2:08 PM

Just to play devil’s advocate: you can’t compare Qwen to a (proprietary/closed source) hosted model and deduce that Qwen is overthinking, as Qwen gives you the full reasoning/thinking trace while all the proprietary models now give you only a summary “to prevent distillation”, making it hard to properly compare apples to apples here.

show 1 reply
dannywtoday at 1:30 PM

Qwen thinking is really good in Mandarin; and probably natively trained the most there.

Try a system prompt requiring it to think in Mandarin, while still delivering the response in the user’s language.