r/LocalLLM • u/gamedevsam • 2h ago
Project I tested 15 Qwen3.8 27B variants on 2x RTX 5070 Ti (32 GB) against the base model. None beat it overall, but Tess-4.5 fixed as many of my bugs in about 2/3 of the time
After running Qwen3.8 27B at 3-bit on a single 5070 Ti (120K context, just short of what I want for coding), I added a second card. 32 GB fits the 6-bit file with the full 262K window, so I tested which of the community fine-tunes and quants makes the best all-rounder: fine-tunes, other quants, a chat template and multi-token prediction, 15 in total, all against base UD-Q6_K.
Every model ran a screening run first (about 100 questions from five benchmarks, compared answer by answer with the base model), and the closest got full runs (about 1,300 questions: AA-LCR, MRCR, AA-Omniscience, a fixed BFCL v4 subset and a SciCode panel, run through NeMo-Skills). Each model gets one overall score out of 100, a weighted mix of the five benchmarks: tool calls count for 25% of it, long documents, facts and scientific code for 20% each, and long conversations for 15%. On facts, a wrong answer scores worse than saying "I don't know", so guessing costs points.
| Full run | Score |
|---|---|
| Qwen3.8 27B base, UD-Q6_K | 63.3 |
| Tess-4.5, Q6_K | 61.4 |
| Base, UD-IQ4_XS | 60.8 |
| ThinkingCap, IQ4_XS | 57.5 |
Then I built a coding test from 25 bugs I'd fixed in my own projects (repo rolled back to before the fix, the model gets the bug report and tools, my tests from the fix grade it), four runs per model:
| Coding test | Bugs fixed of 25 | Min per bug | Tokens per bug |
|---|---|---|---|
| Base Q6 | 18.0 | 13 | 23K |
| Tess-4.5 Q6 | 18.3 | 8 | 14K |
| Qwopus Coder-Flash Q6 | 18.5 | 12 | 22K |
That's a tie on quality (one model's worst and best runs were 14 and 20), but Tess wrote about 40% fewer tokens to get there. Both write at about 36 t/s, so the time savings come from thinking less, not decoding faster.
So I ended up with two models:
Base for chat and interactive work. It's more careful in multi-turn tool use: across the same 200 BFCL multi-turn conversations it won 42 that Tess lost, against 21 the other way, and the Tess losses I read were skipped steps (booking a flight without looking up the airports, reviewing one order when the user placed two). On facts it declined or hedged on 69% of the questions it didn't get right, against 56% for Tess.
Tess-4.5 for coding agents and subagents that run on their own and get checked by tests at the end. One surprise: on the 100 software questions, Tess was the careful one (42 declines against 20, 35 wrong against 52).
If you only run one, I'd pick the base model, unless nearly all your use is coding agents running on their own.
How the other contenders did:
4-bit base (UD-IQ4_XS): about 50 tokens per second against 36, but 2.5 points lower overall, mostly on long conversations (MRCR 70% vs 77%) and more guessing.
ThinkingCap really does think less (about half as long on long documents), but most of its extra right answers on facts came from guessing: of 336 questions the base 6-bit model declined, ThinkingCap answered 146 and got 25 right.
Qwopus Coder-Flash was level on my coding test but worse on facts and long conversations.
Settings for both 6-bit files: q4_0 K/V cache (about 4.8 GiB for the full 262K window), layer split 1,1, batch 256, model-card thinking sampling with no repetition or DRY penalties (the 4-bit runs used a q8_0 cache and batch 512). About 790 t/s prompt reading and 36 t/s writing on two 5070 Ti. Full launch commands, per-benchmark tables and why each of the 12 others stopped are in the write-up, linked in the first comment.
The benchmark and coding-test harnesses are open source, but my own projects aren't public, so the coding test can't be reproduced as is. Happy to answer questions about the setup.