Unsloth Dynamic 3.0 GGUFs

(unsloth.ai)

70 points | by jonesy827 1 hour ago

8 comments

  • xlayn 1 hour ago
    Hey Unsloth, your gguf are the first ones I look for when I want to download a gguf model. Today I was trying in fact to see, what's the smallest Qwen3.8-27B that I could run and get good results, say restricting it to 16GB of ram.. so I went, pick up the Qwen3.8-27B-UD-IQ2_XXS.gguf and them BAM, error on MTP... now I understand why after reading your announcement. Beyond the space saving, why removing the MTP? improves speed exactly for the group that could benefit from it.
    • mike-the-brain 1 hour ago
      you can still have it, no?

      > We also removed the MTP module from smaller quants under UD-Q2_K_XL (8.37GB and lower) to converse around 500MB of disk space - you can use the Q4_0 MTP separate module if needed

      • xlayn 29 minutes ago
        my bad, you are totally right, thanks!
  • QuantumNomad_ 15 minutes ago
    Is it possible to use a model that needs around 64 GB VRAM if you have four GPUs with 16 GB VRAM each?
    • sharmajai 1 minute ago
      I am getting 14 t/s on my 16GB card with the UD-Q3_K_XL quant at full context. Model link: https://huggingface.co/unsloth/Qwen3.8-27B-GGUF
    • segbrk 6 minutes ago
      Yes, but unless they support NVLink (they don't), it's quite slow.
    • charcircuit 7 minutes ago
      Of course. Models don't actually require VRAM. Nor do they require regular RAM. You could have 1 GB of RAM and swap the model to disk as you need different parts of it. And if you didn't have enough disks you could access weights via a network connection.
  • mike-the-brain 1 hour ago
    Might be off-topic but: is it possible to perform such a quantization on Apple devices? Something like Mac Studio Ultra M1 (even if it would take weeks/months)?
    • smcleod 8 minutes ago
      Unsloth use a property dataset they don't release, however you can indeed create quantisation locally on your machine and it's pretty easy, llama.cpp comes with everything you need.
  • throwa356262 58 minutes ago

       "We also made some smaller UD-1bit quants with UD-IQ1_S being 6.2GB (without MTP) which retain around 72% top-1% accuracy yet being 89% smaller"
    
    
    This is crazy! But has anyone tried these lower quants on real projects?
    • kennywinker 48 minutes ago
      Not 1-bit, but I’m getting pretty good results with some light coding using unsloth’s previous 2-bit quant of qwen3.8-27b. With these new quants i may be able to bump up to 3bit, tho it’s already running so slow (15tok/s average for the first 32k of context) that the speed hit might make it not worth the extra smarts
  • tetsuo420 38 minutes ago
    It seems the NVFP4 quants have a preview version of this Unsloth Dynamic 3.0. Is this close to the finished version, or would it be better to switch to one of the newer quants?
  • jadbox 52 minutes ago
    The new IQ4XS has been working pretty well so far on 4090 16gb.
    • kamranjon 38 minutes ago
      What size context are you able to squeeze in with less than 2gb of headroom? I have had some luck using a quantized kv cache but i fear that also decreases overall quality.
  • spwa4 35 minutes ago
    No MLX versions for 3.8 though.
  • lostmsu 25 minutes ago
    Cool. Now run TerminalHard and compare to unquantized 27B.

    KLD of 1%, or similar error metric that multiplies, on 10000 tokens would give accumulated error of 2,000,000%