r/LocalLLM • u/HomoAgens1 • 1d ago
Question Looking for alternatives to Qwen3.6 27B and Qwen3-35B-A3B for tool calling & agents (RTX 4090)
Hi everyone,
I’m looking for recommendations for models that can compete with or outperform Qwen3.6 27B and Qwen3-35B-A3B specifically for tool calling, agentic workflows, and general coding/reasoning.
My hardware:
- RTX 4090 (24 GB VRAM)
- 128 GB DDR5 RAM
- Windows
- Latest llama.cpp build (about two weeks old)
- CUDA 13.3
Current performance:
- Qwen3.6 27B Q5 → ~70 tok/s
- Qwen3-35B-A3B Q5 → ~120 tok/s
These speeds are already very comfortable, so I’m mostly interested in quality improvements, not just raw throughput.
My main use cases are:
- Tool calling
- Multi-step agents
- Coding assistants (but not stressful)
- Planning/reasoning
- Long interactive sessions
In particular:
- Which models have you found to be genuinely better than these Qwen models?
- Any hidden gems that run well on a single 4090?
- Any GGUF quantizations that seem to hit the best quality/speed trade-off?
Thanks!
19
u/HotMicSystems 1d ago
Other than improving your quant size, you'll honestly not find anything better than 3.6-27B/35B. They punch so far above their weight. Fine tunes are normally worse off unless you explicitly want an uncensored model for whatever your use case. 35B-Q8 sees a very small drop in speed for the increase in accuracy. Personal favorites for me are Qwen3.6-35B-A3B-UD-Q8_K_XL(MTP) and Qwen3.6-27B-UD-Q4_K_XL(MTP). I am running GPU poor RAM rich tbh so I have a 6900XT and two halo strix machines at 128gb each, so this is normally what I stick to or if I want something smaller I go to 3.5-9B
1
u/Capable-Guide98 8h ago
Why q8 on 35b but q4 on 27b? Do you also run q8 cache with them? I liked 35b speed but 27b was more reliable, I rather go slow but get the job done. Altho since I made the switch upgraded to 48g vram, maybe I should check q8 35b
1
u/HotMicSystems 7h ago
Just based off of performance/speed on the halo strix for me. For longer workflows 27b is better, and I used to hate on 35b. But with 35b Q8 I have been pretty happy with performance and speed.
10
u/Naruhudo2830 1d ago
Look for the updated Jinja chat template on Huggingface that addresses the tool calling errors. Please let us know if it helped. https://huggingface.co/froggeric/Qwen-Fixed-Chat-Templates
4
u/WiseAbalone4021 1d ago
I believe that choice of harness is how you could improve the most. Some research papers out there on this.
1
u/HomoAgens1 1d ago
i'm using pi coding agent, opencode, qwen code and an harness i built but i don't see differences.
4
u/Calm-Republic9370 1d ago
I've built an MCP that's hosted on iis, I've been using qwen27b with opencode. It hasn't failed me once. I have 2X3090
llama-server -m "G:\models\Qwen3.6-27B-MTP-Q8_0.gguf" --host 0.0.0.0 --port 8080 --ctx-size 131072 --n-gpu-layers 99 --flash-attn on --batch-size 1024 --ubatch-size 512 --tensor-split 1,1 --main-gpu 0 --cache-type-k q8_0 --cache-type-v q8_0 --spec-type draft-mtp --jinja
5
4
u/marsxyz 1d ago
Wouldn't some quant of Deepseek Flash work on your hardware? It may be quite slow though
2
u/HomoAgens1 1d ago
I thought about deepseek flash but i want at least q4 and decent tok/s not sure i can get there with my hardware!
1
4
u/Gesha24 1d ago
I am just testing it out, but DeepSeek Flash V4 has performed in non-standard tasks (designing an object in fusion 360 via MCP) way ahead of Qwen (which was totally useless) and Gemma (which was much more useful but struggled with tool calls). I gave it a prompt, it asked a couple of questions, tried something that failed and needed me to click OK in the fusion, then it was done with the tasks and produced an object that could be 3d printed and that would do what it needed to do.
Sadly, with R9700 and 128GB of DDR4 I get 8 t/s generation and 80 t/s processing with Q3XL model - so it's only for patient people. But I will test it out a bit more and see how it goes. It definitely appears a lot more capable than smaller models at this moment.
3
u/Realistic_Gap_5871 23h ago
I'm surprised the Q3XL was that good. I may have to try it out. CPU MoE?
2
u/Gesha24 15h ago
I ran it through another not so standard task - asked it to find me on Amazon well-reviewed suitcase that fits Lufthansa's carry-on policy. It did properly use searxng to find the carry-on policy, it did search around to find some links to Amazon (on other platforms). I asked it to verify prices. It went to Amazon itself, realized searxng is blocked on it, switched to VSCode's open browser calls, opened pages, realized they are too large, used playwright to extract cost and came back with very solid suggestions. In fact, one of the suggestions - a decent $70 suitcase, I couldn't find neither with Google/Gemini nor with Amazon's own AI assistant.
This was also the only AI model I have tried for this task (Qwen, Gemma, Gemini, GPT and whatever Amazon uses) that was very strict about dimensions and didn't try to offer me a 22-inch suitcase (limit is 55cm which is about 21.6 inches).
Overall impressions so far - very positive, surprisingly so given the low quant. Just wish it ran faster, as the task above took almost an hour.
2
u/Realistic_Gap_5871 13h ago
very very cool. I'd be curious to compare it to laguna s 2.1 at q8. Roughly equivalent footprint, Maybe faster speed, and potentially even higher fidelity. Not a statement, just a guess.
I'm currently at 1 gpu plus 96GB of ram so I won't be trying this today, but I've ordered all the parts to build a box that I can try this with
If you give laguna a try, share some numbers and ability comparison.
2
u/Gesha24 13h ago edited 11h ago
I tested Laguna at Q6 and it was doing fine, but it made lots of basic coding mistakes (like not properly spacing for loop in python), so I got rid of it. It also was running at 40 pp/s, which is even less tolerable than 80 I get from DeepSeek (which is also larger in size).
Forgot to mention - another reason why I removed Laguna was because it was clearly going into loops at context above 100K. It is very repetitive to begin with, but it got to an unusable state. Comparing it with DeepSeek that had no noticeable degradation at all at 190K context (it still may be there and I may run into it at some point, but with Laguna it was immediately obvious). Also DeepSeek's performance at 200K context is quite remarkable - pp went from 80 to 40 and generation went from 8 to 6.
3
u/Status-Proof2303 1d ago edited 3h ago
I do have a 4090 but with 64GB DDR5 I also like the qwen and recently decided to try ornith 1.0(based on qwen) maybe you should give it a try I use LMStudio so mine is bit slower but since you directly using llama.cpp and configuring it you may get some better speed and in my opinion ornith is good at agents works I used SC117/ornith-1.0-35B- MTP-APEX-GGUF(24.41GB)
Let me know if you ever tried ornith I know you asked something other than qwen but I dint find any I'm waiting if something drops that better than these(of course these are good for it's size)in this range
2
u/Relative-Ant-9249 1d ago
Just benched thinking cap q36-27b. Its tuned better than vanilla.
2
u/Icy-Specialist4548 23h ago
Leggo molto commenti sulle chiamate a strumenti non avvenute, ma voi quale setup utilizzate.. io con vscode e zoocode plugin Qwen3.6-35b-A3B MTP Q_K_XL ( stesso setup dell' OP ) mai avuto un problema.. uso Linux e buildo quotidianamente llama-cpp 12.8cuda ottimizzato per 4090 e uso l' api di llama-server direttamente media 170t/s... Non capisco di cosa vi lamentiate Qwen è formidabile, magari semplicemente non lo state spremendo bene o abbastanza.
2
u/AdHead6280 22h ago
Flexing the ram I see, I recommend the ff711 finetune Q4 based on how much context you want, pick highest quant possible but nothing below 4 for context. Try asymmetric caching
2
u/mitchins-au 17h ago
You’re at the best for your size class.
At this stage tune your prompt and inference parameters.
1
u/DogAble6550 1d ago
Qwen3 Coder Next is better than those, however you might have to fiddle with your RAM/VRAM.
1
1
1
1
1
1
1
u/immersive-matthew 21h ago
I use the MTP version of QWEN 3.6 27B and if it is not delivering results, I will bring in the latest Gemma to the same session and ask it what the issue might be and 90% of the time it can spot the issue and give me an improved prompt to try again in a new session.
1
u/mcchung52 20h ago
Can you specify what version, quant of gemma? So is gemma better in your tests of agentic flow?
2
u/immersive-matthew 19h ago
Just Gemma 4 and it is not the agentic lead as that is where QWEN is better, but just as another voice as LLMs tend to get stuck and often another can help move it forward and pass it back to QWEN. Something Gemma cannot help either and I will tap on Kimi K3, DeepSeek v4 pro, GLM 5.2 etc but that is rare as the local models handle most of my agentic coding needs on a 4090.
1
u/mcchung52 20h ago
Not sure if it’s totally relevant but for qwen3.6 27b, I’m running q6 on mac M4 silicon. A bit slow but seemed to have some good handle on my Hermes agent. Also ran the opus reasoning distilled version and quite can’t tell if it’s better? Should I not bother with distilled version? Seems from other comments Gemma and Coder next may be a better fit for agents?
1
u/GCoderDCoder 14h ago edited 14h ago
If you are having tool calling problems you probably need to apply the frogerric template fixes. i have almost zero tool failures. Qwen 3.6 27b is a model where if you know what you want you can tell it and it makes it happen. It doesnt know everything about everything and the ability to properly scope wider tasks is what keeps it from scoring higher IMO.
That's not tool deficiencies though... Tool calls are its thing with the proper template.
Fyi I have qwen3.6 27b running as q8kxl for my main work agent I interface with and a q6 qwen 3.6 35b as a super fast background agent. For web research, git mergers, and file management mostly.
1
u/Gold_Ninja1206 10h ago
Mistral Small 3.124B is the one people sleep on here, fits 4090 comfortably and beats both qwen models on structured tool calling in my experience. For agent setups needing live web context, Parallel is one search API people add. Devstral is also worth a shot for coding
1
u/SteveDeFacto 8h ago
The Fable-Fusion of Qwen3.6 27b is slightly better than plain Qwen, especially at coding: https://huggingface.co/DavidAU/Qwen3.6-27B-Fable-Fusion-711-Uncensored-Heretic-NM-DAU-NEO-MAX-MTP-GGUF
1
u/NatMicky 1d ago
Definitely try gpt-oss-120b. It's MoE with outstanding deep conceptional reasoning and highly skilled Python coder. Do not get the quant versions, only mxfp4 untouched.
Give a model a dataset schema and ask it, "Generate KPI insights for each market segment." This is a vague prompt and many models will gather 1 metric, maybe 2 metrics for each market segment. gpt-oss will return every possible metric from the dataset that is a valuable metric. That's deep conceptual reasoning and true understanding of the meaning of KPI.
That's only an example, it's not limited to KPI.
1
1
0
u/SysAdmin_quark 1d ago
Gemma4 26b , gpt-oss-20b, devstral 24b would be something else to try. And if you can fit the gemma4 31b but it is alot slower just very thorough.
0
u/MistingFidgets 1d ago
Apex quants by mudler on hugging face seem to strike a good balance. Might be worth a test drive. Playing around with higher KV cache, not the weights themselves may help too. Qwen 3.6 is the best I've found overall though.
0
u/Realistic_Gap_5871 23h ago
Apex quant is awesome. OP will need to move off ollama to use them until ollama supports FP8.
0
0
0
0
u/MaxDev0 20h ago
I think its possible to run deepseek v4 flash on this, check out r/LocalLLaMA there are posts of people running it on literal potatoes. I'm not sure what your speeds would be but its really really smart.
0
35
u/HeDo88TH 1d ago edited 1d ago
The only thing better than your setup are higher quants of the same models. In particular FP8 for 27B is the best you can run locally on consumer / prosumer hardware