Best performing model of qwen3.6 family

#3
by repla73 - opened

It's the best perfoming agentic model in this family and can run 15+ tok/sec on modern cpu's

Thanks for this great work

Finally got around to trying this one the other day while I was without internet (electrician contractors cut fiber by accident) and I have to agree, at least for the Qwen MoEs (I'm pretty fond of a couple of the extra trained 3.5-9B) this one performs really well. Getting over 30t/s with my RTX4060 even at 128K filled context. It did a solid one shot conversion of a complicated batch file to powershell, given some json data it had a couple errors to deal with but practically one shotted a python script to import csv data (hundreds of entries) into the json config.

Like all Qwens on the smaller side, it really does seem to do a lot of "no wait..." in it's thinking πŸ˜†

Finally got around to trying this one the other day while I was without internet (electrician contractors cut fiber by accident) and I have to agree, at least for the Qwen MoEs (I'm pretty fond of a couple of the extra trained 3.5-9B) this one performs really well. Getting over 30t/s with my RTX4060 even at 128K filled context. It did a solid one shot conversion of a complicated batch file to powershell, given some json data it had a couple errors to deal with but practically one shotted a python script to import csv data (hundreds of entries) into the json config.

Like all Qwens on the smaller side, it really does seem to do a lot of "no wait..." in it's thinking πŸ˜†

"coder" version works better without even thinking on. You should try that if you want the faster and more accurate. I created a real-world benchmark and tested. This version thinks much longer, better for planning stuff, coder version is for more agentic tool usage.

Oh nice! I didn't even realize there was a coder and coderx separate version. I just finished pulling the Q6 weights of this to see if they do better than IQ4_XS... maybe I should have saved the space for the alt! πŸ˜†

edit:/ thanks for the heads-up and reply repla!

"coder" version works better without even thinking on. You should try that if you want the faster and more accurate. I created a real-world benchmark and tested. This version thinks much longer, better for planning stuff, coder version is for more agentic tool usage.

They are different and indeed the coder version is much better at multi-turn agentic coding workload.
coderx is more "capable" but it thinks a lot more, about 3x, and it gets lost in long running tasks, it's better only on evaluations and one-shot complex tasks

The best model overall and specifically for multi-turn agentic coding it's still Omnimerge-v4 and by a great margin.
It crushes even the new version, Qwen 3.8 27B

Thanks,
Actually I'm waiting for 3.8 version of Omniverge : ) Do you have plans for that? Please do!

Thanks,
Actually I'm waiting for 3.8 version of Omniverge : ) Do you have plans for that? Please do!

Building it now, will be Omnimerge v6.

Thanks! That's extremely exciting!

The best model overall and specifically for multi-turn agentic coding it's still Omnimerge-v4 and by a great margin.
It crushes even the new version, Qwen 3.8 27B

I'm just happy there is a middle ground between 9B and 40B that I can actually run, getting to compare these models to frontier models is turning out to be a rather fun sidequest.

Personally I'm waiting to see how the hardware shakes out... what form non-gpu iterated hardware will take for large models and whether it will stick to the insane GPU pricing models.

Sign up or log in to comment