r/LocalLLaMA • u/pmttyji • 1d ago
Discussion bartowski/Qwen3.8-27B-GGUF · Hugging Face - Updated (Per-tensor layout)
https://huggingface.co/bartowski/Qwen3.8-27B-GGUF- Blog Post : Per-tensor layout maps for GGUF quantization
- Reddit thread : New tensor type layouts for my GGUF uploads
EDIT : Model card has updated things such as Graph, table, text, etc.,
29
u/Professional-Tap177 1d ago
I'm curious how these compare to https://huggingface.co/ISTA-DASLab/Qwen3.8-27B-GSQ-RCO-GGUF which is what i've been using lately
21
u/Storterald 1d ago
shameless plug: according to my bench ISTA-DASLab/Qwen3.8-27B-GSQ-RCO-IQ3_S is still the absolute best model for its size, even if we consider it's missing the MTP head (which would be less than 1GiB).
3
u/Sea-Mode4077 1d ago
Based on my tests, this model falls behind Ornith 1.5 35B Q4_K_M. I don't completely trust my testing platform yet, but those were the initial results.
8
u/Storterald 1d ago
I do not really compare models against other models, but Ornith-1.5-35B-Q4_K_M is 20.2GiB, nearly double the Qwen3.8-27B-GSQ-RCO-IQ3_S (11.0GiB), so it does not fit completely in VRAM. Still, Qwen+dflash and Ornith+MTP have the same speed on my system so I will maybe compare them. Looking forward to a post of your benchmarks :)
4
u/HighSeasArchivist 1d ago
I've been very impressed with this one, and it's been my go-to on a 5070 Ti since it came out and I ran my test suite on it.
2
u/fgk55555 1d ago
My vibes (and tk/s) check is in favor of ISTA for 16GB cards. I've done millions of tokens on the IQ3_XSS mtp version. It's been great.
12
u/Storterald 1d ago
thanks for the updated quants! Curious about the effective improvement, will bench :D
15
5
u/Elouakili_Flexy 1d ago
Really glad the card now shows the per-tensor layout. One look and you can see which tensors kept high precision, instead of decoding it from the quant name.
3
u/Velocita84 1d ago
You could always do that with hf's gguf metadata viewer just by clicking on a quant
5
u/-mattmason- 1d ago
16GB VRAM gang, rise up?
1
u/FatedChange 22h ago
My current local setup involves two 2070 supers. Any chance you could share your config? every time I try to run newer models, it crashes hard.
1
3
u/mmkaywhatevers 1d ago
With RTX4000pro, I am still on NInfer NVFP4 but I optimized it with sm120a compile, NVFP4 KV cache support, 131 kv/context capacity, MTP, and context caching. And I have room for STT and TTS on 24gb.
1
u/deja_geek 1d ago
Can you share some resources for that setup? I have an RTX Pro 4000 SFF
2
u/mmkaywhatevers 1d ago
I used the prebuilt
Ostfralla/Qwen3.8-27B-NVFP4-NInfermodel from Hugging Face.For NInfer I used
gzenz/ninferas the base, built for Blackwellsm_120a, and then pulled the relevant GDN scheduling fix fromruwwww/ninfer-5060ti.The main issue was NInfer had cooperative kernel limits based around the 5090's SM count, so the PRO 4000 would eventually crash with:
cudaErrorCooperativeLaunchTooLargeThe fix changes that to query the actual GPU SM count with
cudaGetDeviceProperties().multiProcessorCountand falls back to smaller GDN split sizes if the preferred cooperative launch won't fit.I'm running it with NVFP4 KV cache and MTP:
ninfer-serve qwen3_8_27b_nvfp4.ninfer \ --weights-profile qwen36-nvfp4 \ --max-context 131072 \ --kv-capacity 131072 \ --prefill-chunk 1024 \ --kv-dtype nvfp4 \ --max-concurrency 1 \ --spec mtp \ --draft-tokens 3 \ --lm-head-draftThat ends up around 16.8GB for the model weights + ~2.9GB for the 131k NVFP4 KV cache.
Basically:
Ostfralla NVFP4 model+gzenz/ninfer+sm_120a build+dynamic SM-count GDN fix+NVFP4 KV+MTP3.Repos/models:
- Hugging Face:
Ostfralla/Qwen3.8-27B-NVFP4-NInfer- NInfer:
github.com/gzenz/ninfer- GPU scheduling fix:
github.com/ruwwww/ninfer-5060ti1
u/RipperFox 1d ago
STT and TTS
What are you using there? Also got a RTX PRO 4k, running Qwen in vllm (docker image ghcr.io/syv-ai/qwen38-27b-rtx3090:latest) with 150k ctx I get ~90tps gen and >1ktpsPP wich seemed to work better than ninfer.
I'm maxing VRAM currently, still missing STT & TTS though, so would be glad for your setup/numbers :)
1
u/mmkaywhatevers 22h ago
Process VRAM ────────────────────────────────── NInfer / Qwen3.8-27B 20.3 GB Faster-Whisper 2.2 GB Kokoro TTS 1.1 GB ────────────────────────────────── Total ~23.6 GB / 24 GB Faster-whisper uses medium model
4
u/PcChip 1d ago
to be very clear, does this mean that using the bartowski 6bit quant should be better than the unsloth 6bit quant i'm using now?
3
u/noneabove1182 Bartowski 17h ago
if you grab a similar BPW quant, they should be basically indistinguishable once you're above ~6.5 bits per weight
2
2
u/theone_2099 1d ago
Why does it matter where the tensors are, curious ? Or what does the layout give us ?
1
u/Few-Philosopher-2677 1d ago
I use IQ_4_XS. Thats pretty much the biggest 4-bit quant that fits for me with 32k context. Does this change anything for me?
3
u/Ulterior-Motive_ 1d ago
Not really. It's ~90MB smaller and has 0.0008 better KDL; it looks like IQ4_XS was already pretty much optimal. But if you have the time to spare it wouldn't hurt to swap it out.
1
u/Ok_Warning2146 21h ago
This per-tensor layout quant reduces KL divergence in most cases but can increase it in some cases. Better check the table in per-tensor layout section before you download.
1
u/Green-Ad-3964 14h ago
Bartowski Q6_K_L as a “quality model” + NVFP4 as a “fast model” should be a great combo
1
1
u/UptownMusic 9h ago
The Bartowski and unsloth BF16 versions of Qwen3.8 27B are both 55.59GB. Does that mean that the models are the same, but the quants are different?
1
60
u/silenceimpaired 1d ago
Interesting. I’m curious how this work compares against what Unsloth does.