[–] [S] 5 points 20 hours ago*

For a 16Gb card I use UD-IQ4_XS with 94208 of context and Q4 for KV cache. But I don't have desktop on this GPU, so you'll need to either reduce the context size or use a 3 bit quant.

It's is a dense model, so RAM is irrelevant. It will be too slow if the model leaks into RAM. You'll need to put all layers on the GPU.

  • source
  • parent
  • context
  •  

    Hey guys! Today, we're releasing the highest accuracy Qwen3.8-27B GGUFs.

    Our new Unsloth AI Dynamic V3.1 GGUFs lead by 5–10% on average across Terminal Bench, DeepSWE & more benchmarks. We’re working on even better version of Dynamic quants for Qwen4

    Run on 12GB+ RAM setups.

    To compare GSQ-RCO and Exllama-v3, we had to exclude the token embedding layer from the x axis, as Exllama-v3 uses BF16 for it. If you consider the full download size and total RAM usage for Exllama-v3, then adding the BF16 embedding table and including all embedding sizes changes the plots. Our main plots's x axis removes the embedding layer sizes from all quant providers. However on pure RAM usage and disk space usage vs accuracy, the below plot in the comments the true reflection of actual usage.

    GGUF: https://huggingface.co/unsloth/Qwen3.8-27B-GGUF

    Blog: https://unsloth.ai/docs/models/qwen3.8

    From their Reddit post.

    [–] 2 points 3 days ago* (last edited 3 days ago) (1 child)

    Yeah, 27B only usable if you can fit it entirely in VRAM. Only MoE models are fine to split, like the mentioned Qwen 3.8 Flash Next. Even though it's large, only the active 6B parameters needs to be located in VRAM, the rest can be in RAM and SSD.

  • source
  • parent
  • context
  • view more: next ›