Unsloth reports DeepSeek-V4.1 GGUF benchmarks above GSQ-RCO on several tests
Reported by r/LocalLLaMA4 sources ↓
Unsloth says its DeepSeek-V4.1 Dynamic 3.1 GGUFs scored more than 10–20% above GSQ-RCO on several agentic benchmarks. It reports using 512K context for those tests and 128K for general tasks.
Key points
- Unsloth says it ran DeepSWE, Terminal Bench, Automation Bench, HLE and SciCode at 512K context
- Unsloth reports 35.1 billion benchmark tokens, 27 times its previous total
- It says it repeated AIME 2025 runs 64 times and DeepSWE and Terminal Bench runs three times each
- Unsloth published its Dynamic 3.1 GGUFs and benchmark methods online
Sources
- r/LocalLLaMARead ↗Unsloth vs GSQ-RCO - 512K context DeepSeek-V4.1 GGUF benchmarks Terminal Bench
- r/LocalLLaMARead ↗Unsloth Qwen3.8-Flash-Next GGUFs V3.1 Update (November 4th 2026)
- r/LocalLLaMARead ↗New Qwen3.8-Flash-Next Unsloth Dynamic V3.1 GGUFs
- r/LocalLLaMARead ↗Unsloth v3.1 QFN IQ4_XS fails tool calls very frequently
Details
Unsloth's November 2 post reports that its DeepSeek-V4.1 Dynamic 3.1 GGUFs scored more than 10–20% above GSQ-RCO on DeepSWE, Terminal Bench, Automation Bench, HLE and SciCode. The post does not provide the individual benchmark scores in the supplied text.
Unsloth says those agentic tests used 512K context, while its other 14 benchmarks used 128K. It reports running 35.1 billion tokens of benchmarks, compared with 1.3 billion previously, and says it repeated AIME 2025 runs 64 times and DeepSWE and Terminal Bench runs three times each.
For Terminal Bench 2.1, Unsloth says it used mini-swe-agent and a 150-step maximum, and excluded seven of 89 tasks that could not pass on its infrastructure. The post also gives its own statistical estimates of GSQ-RCO quantization recovery; no GSQ-RCO response or independent verification is included in the supplied article.
Written from coverage as of