The hybrid quant employs different quantization levels on a per layer basis to enable
both high performance and small file size at the same time. The quants employed are all K to avoid
slow CPU or older GPU processing of IQ quants. For this file an extended layer definition E quant Q4_E_H is defined as follows:
The quant was evaluated for strong reasoning performance across a curated set of test prompts. Experimenting with different
quant levels determined this model to be quite sensitive to losing coherent reasoning ability when quantization to
lower bit precision levels. The Q4_E_H quant is sized to be able to run in 24G VRAM with some space left for context.
In tests the model shows significant overthinking on some problems. It fared well against some simple IQ test
type problems evidencing a fairly strong latent space / well curated traing set for only 30G class model. If a problem does not fall into its latent solution space
it can just fall into a endless rep loop typical of other thinking models. It clearly uses forced introspections in its RL training
as an attempt to increase its gen reliability and if the model is unable to find consistency in the forced double/triple/quadraple+ checks it can get stuck
in reasoning loops with greedy sampling.
The original Q4_K_H quant made for GLM-4.7-Flash is also available. This quant benches well but it does not do as well as Q4_E_H across the curated
set of test prompts used to optimized the layer quants. It is defined using E quant MP layer definition syntax as follows:
This is a RL trained Moe thinking model. The layer quants for this model were optimized over a set of test/eval prompts using
greedy sampling. The model overthinks and occasionally get stuck in infinite generations. When it can solve a problem it normally
does a very good job. It appears to have been trained with forced introspections and possibly given less reward for efficient
solutions than other GLM based thinkers as it will spit out a ton of tokens with many unecessary reflections.
To bypass think mode inject a think start and stop at the beginning of gen or modify the assistant prompt template to add
THINK_START and THINK_STOP at the end of the assistant template:
THINK_START="<think>"
THINK_STOP="</think>"
These tokens must be tokenized as special tokens.
The model can be run on consumer grade hardware using tensor offload to CPU i.e.
OT="-ot exps=CPU -ngl 99"
The model should not be speculated when using dominant CPU offload since CPU does not have enough parallel hardware to benefit in
large speed increase from processing larger batches of tokens. Negligible speedup was found Using Qwen3 0.6 as a speculator so
speculation is also not recommended with full GPU offload.
It is possible to partially offloading experts to CPU i.e. experts 18-46 only are offloaded to CPU:
This partial offload is not recommended as it results in slower gen most likely related to extra shuffling of data between GPU and CPU in this mode,
the exact cause of inefficiency was not investigated since -ot exps=CPU gives very usable gen rates by itself even on an older CPU (9900k/DDR4 mem).
Approx performance with llama.cpp b9404 usings 4070 (12G VRAM) GPUs with 9900k (128G RAM) CPU :
CONFIG
QKV
NKV
gen tps
Comment
-ot exps=CPU
F16
180k
21
llama.cpp 9404
-ot exps=CPU
Q8_0
198k
21
""
-ot exps=CPU 18-46
F16
80k
18
""
RPC (2x4070)
F16
80k
76
""
" "
Q8_0
144k
75
""
Long context test from https://thireus.com/REDDIT/Qwen3_Runescape_Massive_Prompt.txt was run on Q4_E_H at Q8_0 QKV and although the model was heading
toward the right answer it then got stuck in a long rep loop. It handled a simple needle in haystack long context test with no issue.
Prompt processing slows down to a crawl heading toward 100k+ tokens even with full GPU offload over RPC.
The Q4_E_H model was tested against a small set of code gen prompts using greedy sampling and found to be quite strong in its ability
to generate working programs with both think mode enabled or disabled suggesting it was intentionally tuned for a strong coding base
in its pretrain/postrain/RL optimization. It got stuck in a rep loop during code gen on one of the test prompts but shutting off think
mode allowed the model to successfully generate working code on the test prompt.