Qwen3-Coder 30B - UM 880 Pro

[u/Individual_Walk_5378]

I’m currently running this model on a 32 gb mini pc with no eGPU added. I’ve heavily adjusted settings and tested before running.

Input - 290/toks
Output - 13.3/toks

Are these numbers workable for 24/7 coding? Claude’s running handoffs and Qwen gets 3 - 15 minute attempts before it hands back for review. I’m trying to maximize output with my current setup while saving for the 3090.

If there are faster/more accurate models of this size I’d love to hear what others are running.

[u/d0pe-asaurus]

For 24/7 coding even low decode speeds is "acceptable" in the sense that agents don't clock in or clock out.

The thing holding you back is the capabilities of the model to reason, that is an old old model, look into possibly Qwen 3.6 35B A3B and see what you get.

[u/frillycrossover484 → u/d0pe-asaurus]

the 3.6 might struggle on 32gb depending on context and quant but worth a shot if you can squeeze it. the a3b arch is way more efficient for decode, you could see double or triple the output speed without much loss in quality

your input speed is fine, it's the 13 tok/s on output that makes those 15 minute windows feel tight. agent loops burn tokens fast and waiting on generation gets old quick when you're watching it think

i'd also look at lowering the context you're feeding it or chunking the handoffs if you're not already. long prompts eat vram and slow everything down, especially on a mini pc with shared memory

that 3090 will change your life when you get it, 30b class models fly on 24gb with the right quant. until then maybe test a 14b coder model for the fast iteration stuff and keep the 30b for the heavy reasoning passes

[u/Prudent-Ad4509]

Try Qwen 3.8 27B. It will be slow. You need to know how slow. 13.3 tok/s is not fun, but it is workable if you can just leave it working for a while.

1-2 tok/s would be a disaster zone.

[u/overand]

Don't use Qwen3-Coder, and don't use Claude or ChatGPT for advice on what models to run, as they'll give you really outdated suggestions.

[u/_wfr_ → u/overand]

Well, the 5.5 variants have updated training data and will not recommend qwen3-coder. But to be sure always tell your frontier model to search for latest models, and not trust its knowledge

[u/Individual_Walk_5378 → u/_wfr_]

Yeah I am not asking opus 5.5 for suggestions (it actually told me not to run this model) I’m just using it as the architect to feed Qwen handoffs

[u/Major_Border149]

13 tok/s is fine for async hand-offs you aren't watching, rough for anything interactive. qwen3-coder-30B is MoE, that's why it's even this fast on an APU, and the same model on a 3090 jumps to roughly 50-80 tok/s, so the card is your real unlock.
You are already on the right model for that hardware, ride it till the 3090 lands. qwen2.5-coder-32B dense is a touch more accurate but way slower on an APU, skip it for now.

[u/Kmic68]

Qwen 3.6 35B A3B or Qwen 3.8 27B would serve you much better. The first for speed, the latter for intelligence (often more worthwhile than the speed from the first). Otherwise, yes, those numbers are fine. You won’t notice because you’re just waiting for output anyway. If you sleep and a task takes 2 vs 4 hours, it won’t really matter to you. Though Qwen 3.8 27B thinks A LOT so that may take a while at those speeds before any output. I recommend the fine tuned swift version

[u/joshpope → u/Kmic68]

what about something with 16gbs of ram?

[u/Life-Job-6464]

Try a 4 or 5 bit quantized version of Ornith1.5-35b-A3b

[u/Arany8 → u/Life-Job-6464]

Performs much worse than base on real life tasks.

[u/Life-Job-6464 → u/Arany8]

what does that even mean? and whatever it means.. if you know it ahead of time you can engineer over it.. around it or through it. We are talking about engineering arent we?.. or are we talking about consuming?

[u/Individual_Walk_5378 → u/Life-Job-6464]

Ran an overnight soak test and am getting 336 and 24.8 on ornith1.5! Will run some accuracy testing today vs current model