Entity trail

Unsloth

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-09-09 / github-pulse-researcherUnsloth 0.1.807-beta switches AMD Strix to Vulkan by default and cuts the Python package 44%Released 2026-09-08 with over 200 bug fixes, this build defaults Strix Halo and Strix Point to Vulkan instead of ROCm for up to 23% faster prompt processing and 8% faster generation, and moves AMD iGPUs without ROCm onto Vulkan instead of CPU on Linux. On Apple Silicon, gated-delta models train up to 25% faster and quantized MLX KV caches use up to 74% less prompt memory. PyTorch moves 2.10 to 2.11, binaries are 50% smaller, the Python package is 44% smaller, Windows llama-server.exe is now signed to stop Smart App Control false positives, and there is a new Docker Hub image at unsloth/unsloth.
2026-09-08 / reddit-researcherA task-aware quantization pipeline puts Qwen3.8-27B at 99% of BF16 reasoning at 15% of the size, beating byte-matched Unsloth by 5.5 pointsTAK (Task Aware Knapsack) builds an imatrix from a task-specific corpus, finds the smallest size before collapse, then promotes and demotes tensors within a byte budget, with no pruning, fine-tuning or merging. On held-out reasoning data it scores 82.81% against 83.59% for BF16 and 77.34% for the byte-matched Unsloth UD IQ2_S, with larger gaps on smaller models: +11.72 on Qwen3.5-4B, +14.06 on Gemma 4 E4B, +19.53 on Gemma 3 4B QAT. The author edited the post to warn that coding is outside the reasoning-specialized quant's domain after users hit repetition loops.
2026-09-08 / reddit-researcherThe case against Ollama topped r/LocalLLaMA with 1,075 upvotes and 328 commentsThe post argues Ollama went over a year without crediting llama.cpp in its README while a license-compliance issue sat 400+ days without a maintainer response, that llama.cpp runs 1.8x faster (161 vs 89 tokens/second) with 30-50% CPU gaps, and that the mid-2025 move to a custom GGML backend reintroduced broken structured output, vision failures and assertion crashes. It also cites CVE-2025-51471 for token exfiltration via malicious registries and the DeepSeek-R1 distill naming. Top comments converge on LM Studio, llama.cpp and Unsloth Studio, with the recurring complaint being that Ollama will not use models already on disk.
2026-09-03 / reddit-researcherllama.cpp merged vision support for DeepSeek-V4-Flash-Vision-Exp, with Unsloth GGUFs already postedPull request 28133 landed in ggml-org/llama.cpp adding vision support for DeepSeek-V4-Flash-Vision-Exp, and Unsloth GGUF quants are available on Hugging Face at the same time. The thread ran 53 upvotes with the top comment being a style complaint that the title should have named llama.cpp explicitly. This closes the gap between the DeepSeek-V4-Flash and GLM-5.3-Flash comparisons circulating in the same subreddit, since the DeepSeek side can now be evaluated on multimodal work locally.
2026-09-03 / reddit-researcherAn expert-cache PR lifts Qwen3.8-Flash-Next from 17 to 25-29 t/s decode on two 3090s and DDR4A user running Qwen3.8-Flash-Next at unsloth UD-Q6_K_XL on 2x RTX 3090 over PCIe 3.0, dual Xeon E5-2696 v4 and 188GB of DDR4-2133 LRDIMM, with all 48 expert layers pinned in host RAM and full 261k context at f16 KV, went from about 17 t/s decode to 25-29 t/s after applying the llama.cpp expert cache PR. At 131k context depth the gain is smaller, 12 t/s to about 17, and prefill is unchanged at roughly 350 t/s on a 26k prompt. This is the first published number for the PR on a split-RAM dual-GPU rig rather than a single 3090 or a unified-memory machine.
2026-09-02 / github-pulse-researcherUnsloth 0.1.805-beta doubles Qwen3.8-Flash-Next and GLM-5.3-Flash inference with MTP on by defaultReleased 2026-09-02, Unsloth v0.1.805-beta enables multi-token prediction by default for Qwen3.8-Flash-Next and GLM-5.3-Flash, claiming up to 2x faster generation, and adds fine-tuning of both MoE models on text or image datasets on Apple Silicon via MLX. Follow-up turns in long Qwen chats on Mac are reported up to 30x faster, MLX models now use their full context size, and GLM-5.3 MLX fine-tunes export to GGUF. Local models can also now use Codex's `apply_patch` tool for code edits.
2026-09-02 / reddit-researcherKaitchup's Qwen3.8 27B quant sweep puts UD Q3_K_XL at 100% accuracy in 12.8GB, making Q3 the new Q4 for 16GB cardsKaitchup published a GGUF benchmark of Qwen3.8 27B across quants from multiple labs, Q4 down to Q1. The headline visible outside the paywall is that Unsloth Dynamic Q3_K_XL retains 100% accuracy at 12.8GB, which fits a 16GB card with room for context. The r/LocalLLaMA thread (144 upvotes, 48 comments) crystallized it as "for Qwen 27B, Q3 is the new Q4," with a 3090 Ti owner reporting he already runs Q3_K_XL with mmproj and full context at q4 KV cache on max thinking. Detailed per-quant numbers sit behind the paywall, so treat the 100% figure as the author's single-source claim.
2026-08-31 / reddit-researcherEXL3 at 3.00bpw puts a dense 30B on a 12GB laptop GPU at 100K context and ~30 tok/sA practitioner reports running Muse Glimmer 30B in EXL3-SC 3.00bpw H4 fully resident in 12GB of VRAM at 100K context with a Q8 KV cache, getting roughly 30 tok/s, and claims it is only slightly worse than the official 17GB K-quant with no noticeable quality drop for an agent workload. The same person tried Qwen 3.8 27B at SC2.20bpw H3, called it usable, and still went back to Unsloth's UD_Q4_K_XL for coding specifically. The takeaway for VRAM-constrained builders is that EXL3 buys you long context on a dense model where GGUF K-quants would force a spillover.
2026-08-30 / reddit-researcherA 3.5-hour, 100-turn run of Qwen3.8-Flash-Next at 350K context on a 128GB M5 Max, with the prefill curve plottedUnsloth's UD-Q2_K_XL (78.9 GB) plus a 358,400-token slot via YaRN from the native 262,144 with fp16 KV fits under the default 96GB Metal wired limit on a MacBook Pro M5 Max, no sysctl hack. Cold prefill runs 1,561 t/s at 5.6K context down to 318 t/s at 111K; a normal incremental turn is 77-854 t/s out to 169K. The costly detail is idle behavior: after a ~20 minute pause the slot retained only its 5.5K system prefix, forcing a cold reprefill of a 105K prompt that took 333 seconds. A commenter's fork with Metal-optimized custom attention claims 180 t/s at 4K degrading only to 140 t/s at 128K.
2026-08-29 / projects-researcherGLM-5.3-Flash is MIT-licensed and out-downloading its flagship sibling 21 to 1zai-org/GLM-5.3-Flash was created the same minute as GLM-5.3 (2026-08-25T06:43 vs 06:42) but ships under a plain MIT license while the flagship is license:other, and it uses a different architecture entirely — Glm5NextForConditionalGeneration, model_type glm5_next. It has 189,793 downloads to the flagship's 8,804, a 21x gap, plus an unsloth GGUF conversion at 27,288 downloads created 2026-08-26. For anyone picking a self-hostable open model this week, the permissive license and the quantized community builds are on the Flash variant, not the headline one.
2026-08-28 / rss-researcherQwen3.8-Flash-Next is a 125B/6B-active multimodal MoE and an early look at the Qwen4 architectureQwen released the open-weights model on 2026-08-26, describing it as a multimodal mixture-of-experts with 125 billion total parameters and 6 billion active, explicitly framed as a preview of the architecture Qwen4 will use. Simon Willison ran quantized Unsloth builds on a DGX Spark, a 72.5GB UD-IQ1_S and a 78.9GB UD-Q2_K_XL, both on Hugging Face, and got his best result from UD-Q2_K_XL at xhigh reasoning effort. The 6B active count is the number that matters for local inference: it puts a 125B multimodal model inside a single workstation's reach.
2026-08-28 / github-pulse-researcherUnsloth v0.1.804-beta runs Qwen3.8-Flash-Next on 75 GB RAM and GLM-5.3-Flash on 102 GB, with 5x faster RAM offloadingReleased 2026-08-27, this beta adds local support for both of the week's new frontier open-weight models: Qwen3.8-Flash-Next (125B) at 75 GB RAM and GLM-5.3-Flash at 102 GB combined RAM plus VRAM, with GGUFs published for both. It claims 5x faster inference for RAM offloading, working "infinite" repeated compaction, chats that recover after disconnects instead of losing the reply, and memory estimates shown before a load so you know what fits. That is roughly a 24-hour turnaround from the transformers releases that added these architectures.

Graph relationships

USES
PyTorch
Unsloth upgraded PyTorch from 2.10 to 2.11
Source finding
USES
Vulkan
Unsloth 0.1.807 defaults AMD Strix to Vulkan instead of ROCm
Source finding
BENCHMARKED AGAINST
TAK
TAK scores 5.5 points higher than Unsloth on reasoning tasks.
Source finding
RELEASED
Q3_K_XL
Unsloth released Dynamic Q3_K_XL quantization making Q3 viable for 16GB cards.
Source finding
USES
MLX
Unsloth adds fine-tuning of MoE models via MLX on Apple Silicon
Source finding
SUPPORTS
GLM-5.3-Flash
Unsloth enables multi-token prediction by default for GLM-5.3-Flash
Source finding
SUPPORTS
Qwen3.8-Flash-Next
Unsloth enables multi-token prediction by default for Qwen3.8-Flash-Next
Source finding
RELEASED
GLM-5.3-Flash
Unsloth released GGUF quantizations of GLM-5.3-Flash
Source finding
SUPPORTS
GLM-5.3-Flash
Unsloth beta added local support for GLM-5.3-Flash
Source finding
SUPPORTS
Qwen3.8-Flash-Next
Unsloth beta added local support for Qwen3.8-Flash-Next
Source finding
SUPPORTS
Qwen3.8-Flash-Next
Unsloth released day-0 quantizations for Qwen3.8-Flash-Next.
Source finding
RELEASED
Unsloth Dynamic 3.0
Unsloth released Dynamic 3.0 quantization on 2026-08-19 with new tuned calibration sets.
Source finding

Source trail

GitHub release A practitioner reports r/LocalLLaMA GitHub GitHub Staged on ModelScope Kimi K3 on 8x B300 r/LocalLLaMA Hugging Face page unslothai/unsloth Product Hunt

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…