Unsloth vs GSQ-RCO, 512K context DeepSeek-V4.1 GGUF benchmarks Terminal Bench
Summary
Unsloth published benchmark results comparing its Unsloth Dynamic GGUF quantizations of DeepSeek-V4.1 against GSQ-RCO quantizations. Agentic tests, including Terminal Bench, DeepSWE and Automation Bench, ran at 512K context. General tasks ran at 128K context, across 14 benchmarks in total. Unsloth reports that its files outperform GSQ-RCO and says it ran 27x more benchmark data than in earlier rounds.
The write-up lists its methods: repeated runs to reduce noise, Math Verify and improved graders, the official Terminal Bench graders through Harbor, and mini-swe-agent for the agentic tasks. It excludes 7 of 89 Terminal Bench tasks that failed on its infrastructure, and it rechecks GSQ-RCO's own recovery claims with statistical tests. The documentation page and the GGUF files on Hugging Face hold the full details.
Why it matters
The test results show which quantized open models can handle long, multi-step agent work on local hardware. That shapes which assistants and agents run privately, outside the major hosted platforms. More brand research, comparison and recommendation tasks may run on local models at long context. Teams that want to be found and cited by AI then need to know how those compressed models read and keep long documents. This item is mainly about model engineering, though, so the effect on brand visibility is indirect.
Source
- unsloth.ai/docs/models/deepseek-v4.1-flash the item itself, published by r/LocalLLaMA, created by danielhanchen
- unsloth.ai/docs/~gitbook/site-index Reproducible first-party demonstration, first party
- unsloth.ai/docs/fr/modeles/deepseek-v4.1-flash Reproducible first-party demonstration, first party
- github.com/unslothai/unsloth Public source code or repository
- github.com/ggml-org/llama.cpp/pull/30817 Public source code or repository
- unsloth.ai/docs/models/qwen3.8-next Reproducible first-party demonstration, first party
- unsloth.ai/docs/jp/moderu/deepseek-v4.1-flash Named expert analysis, or a first-party claim about itself, first party
- reddit.com/r/LocalLLaMA/comments/1xm102d/unsloth_vs_gsqrco_512k_context_deepseekv41_ggufwhere AIOTruth found it
What was checked
- canonical URL taken from the page itself
- read the item page (200)
- https://unsloth.ai/docs/models/deepseek-v4.1-flash: supports the item, tier 2 (Reproducible first-party demonstration)
- https://unsloth.ai/docs/~gitbook/site-index: supports the item, tier 2 (Reproducible first-party demonstration)
- https://unsloth.ai/docs/jp/moderu/deepseek-v4.1-flash: supports the item, tier 8 (Named expert analysis, or a first-party claim about itself)
- https://unsloth.ai/docs/fr/modeles/deepseek-v4.1-flash: supports the item, tier 2 (Reproducible first-party demonstration)
- https://github.com/unslothai/unsloth: supports the item, tier 6 (Public source code or repository)
- https://github.com/ggml-org/llama.cpp/pull/30817: supports the item, tier 6 (Public source code or repository)
Limitations
- Reddit engagement is a discovery signal here, not evidence that the claim is correct.
AIOTruth judgment
The item has Confirmed evidence status because the claims come from first-party documentation, along with a public repository and a llama.cpp pull request. Usefulness, evidence and originality score high. The write-up names its graders, step limits, excluded tasks and statistical tests, so readers can check how the results were produced. Relevance scores 3 because quantization benchmarks touch AI-era discovery only indirectly. The comparison is also published by one of the two competing parties, and Reddit engagement counts only as a discovery signal.
How this score was calculated
| Dimension | Weight | Score | What produced it |
|---|---|---|---|
| AIO relevance | 30% | 3 | no beat terms matched; 2 scope question(s) matched |
| Usefulness | 30% | 10 | 2 artifact(s), 6 actionable marker(s), 2 measured figure(s) |
| Evidence | 25% | 9 | Reproducible first-party demonstration; 6 verified source(s) across 2 domain(s) |
| Originality | 15% | 9 | carries original testing or data; closest archive match 0.074 |
aioRelevance x 0.30 + usefulness x 0.30 + evidence x 0.25 + originality x 0.15. The rubric is published in full on the Editorial Method page. Scoring is deterministic: the same item scores the same on every run.
Review the documentation Open the source
Found something wrong here? AIOTruth corrects material errors openly. Have something we should review? Submit a find.