Views
No views yet
| File | Quant | Size |
|---|---|---|
qwen3.5-9b-dflash-Q4_K_M.gguf | Q4_K_M | 730 MiB (4.68 BPW) |
unknown model architecture: 'dflash'.unsloth/Qwen3.5-9B-GGUF):1llama-server \
2 -m Qwen3.5-9B-UD-Q4_K_XL.gguf \
3 --spec-draft-model qwen3.5-9b-dflash-Q4_K_M.gguf \
4 --spec-type draft-dflash \
5 --spec-draft-n-max 4--spec-draft-n-max — it matters a lot| Config | tok/s | Draft acceptance |
|---|---|---|
| No speculation | 199 | — |
dflash, n-max 15 | 260 | 26.7% (159/595) |
dflash, n-max 4 | 327–366 | 85.6% (308/360) |
n-max 15,
so the effect is backend-independent.llama_init_from_model: failed to initialize the context: dflash requires ctx_other to be set
(this warning is normal during memory fitting)
srv load_model: [spec] failed to measure draft model memory: failed to create llama_context from modeltoken_embd / output tensors — they borrow the target's. The
pre-fit measurement pass loads the draft standalone, before ctx_other is wired up in
common/speculative.cpp, so it always throws. Harmless; the server continues and loads
the draft normally. The only cost is that the draft's memory is not counted during
auto-fit, which can matter on a tight VRAM budget if you let --ctx-size or -ngl be
auto-selected (see --fit-target, --fit off).--target-model-dir
pointing at the target's HF repo (only its tokenizer and config are read, not the weights):1python convert_hf_to_gguf.py z-lab/Qwen3.5-9B-DFlash \
2 --outtype bf16 \
3 --target-model-dir Qwen/Qwen3.5-9B \
4 --outfile qwen3.5-9b-dflash-BF16.gguf
5
6llama-quantize qwen3.5-9b-dflash-BF16.gguf qwen3.5-9b-dflash-Q4_K_M.gguf Q4_K_Mgeneral.architecture = dflash, block_size = 16,
target_layers = [2, 6, 10, 14, 18, 22, 26, 30], sliding window 4096.