This model has MTP (Multi-Token Prediction) layers, and they are included in these quants
MTP layers act as a built-in draft model, letting llama.cpp run speculative decoding for faster generation. To use them, add the following flag to your llama.cpp command:
--spec-type draft-mtp
Note: the MTP layers are stored at Q4_0 in every quant except Q8_0. Imatrix calibration does not exercise them, so the imatrix has nothing to offer these layers, and Q4_0 is chosen for its speed, which massively benefits MTP performance.
Some of these files were built with a layout computed for this model instead of llama.cpp's standard one-size-fits-all rules. A Q4_K_M is still mostly Q4_K; the extra precision goes to the weights this particular model is most sensitive to. The S, M or L in a name says how much of the model stays at the base precision: about 90 % for S, 70 % for M and 50 % for L. An _L name is simply the large size of its family. Q4_K_L is to Q4_K_M what Q4_K_M is to Q4_K_S; Q6_K_S, Q6_K and Q6_K_L are the small, medium and large sizes of Q6_K, with Q6_K_L about halfway to Q8_0. In earlier releases an _L name meant the embedding and output weights were kept at Q8_0; in these files it means the larger size of the base type. There is no size target, so each file's bits per weight is reported rather than promised.
The layout each of these files was built with is published in the layouts/ folder: <file>.tensor-types.txt is the exact --tensor-type-file given to llama-quantize, and <file>.layout.json records how it was computed, including the generator version, the llama.cpp release and the commit, so any of them can be rebuilt. The code that computed them is public at quantization-config; its tag key-3bf8b43e20a68f0b is the exact snapshot these files record. The method is described in this write-up.
Checked on this model before any of these files were released: Q4_K_M reached 0.98×, Q3_K_M 1.05× and IQ2_XXS 0.53× the KL divergence of the standard layout at the same file size.
Layout details
Files built from a computed layout:
Quant
Size
Body bits/weight
File bits/weight
Body kept at base type
Q6_K_L
28.44GB
7.40
7.29
51 %
Q6_K
27.19GB
7.04
6.97
70 %
Q6_K_S
26.00GB
6.71
6.66
90 %
Q5_K_M
24.00GB
6.15
6.15
70 %
Q5_K_S
22.41GB
5.70
5.74
90 %
Q4_K_L
21.69GB
5.50
5.56
50 %
Q4_K_M
20.06GB
5.04
5.14
70 %
IQ4_NL
20.01GB
5.04
5.13
70 %
Q4_K_S
18.89GB
4.72
4.84
90 %
IQ4_XS
17.98GB
4.47
4.61
90 %
IQ3_M
17.04GB
4.20
4.37
50 %
Q3_K_L
16.85GB
4.14
4.32
50 %
Q3_K_M
16.10GB
3.93
4.13
70 %
IQ3_XS
14.92GB
3.60
3.82
90 %
Q3_K_S
14.92GB
3.60
3.82
90 %
IQ3_XXS
14.43GB
3.47
3.70
70 %
Q2_K
12.84GB
3.06
3.29
70 %
IQ2_M
12.53GB
2.93
3.21
70 %
IQ2_S
11.24GB
2.62
2.88
70 %
IQ2_XS
10.56GB
2.43
2.71
90 %
IQ2_XXS
10.32GB
2.36
2.64
70 %
Checked on this model: the computed layout against the standard one, measured by KL divergence against the unquantized model. The ratio compares each computed file with the standard ladder read at that file's own size, so it can differ from the two KLD columns when the two files differ in size.
Quant
Computed layout KLD
Standard layout KLD
Ratio at equal size
Size vs standard file
Q4_K_M
0.0338 ± 0.0009
0.0415 ± 0.0011
0.98×
+4.2 %
Q3_K_M
0.0913 ± 0.0016
0.1152 ± 0.0018
1.05×
+8.1 %
IQ2_XXS
0.3839 ± 0.0043
0.9905 ± 0.0074
0.53×
+8.4 %
How it works: the base type is a floor for every body tensor and a fixed share of the body bytes stays at it (90 % for S, 70 % for M, 50 % for L); the remaining bytes go where a cross-model sensitivity prior, measured by KL divergence against the unquantized model, says they buy the most quality. The embedding and output tensors are sized by their share of the file: a small table is kept at Q8_0, a large one follows the file's bitrate. A K-quant and the IQ quant with the same base bitrate (Q3_K_S and IQ3_XS, Q3_K_M and IQ3_S, Q3_K_L and IQ3_M) come out at about the same size; the IQ file is the GPU-oriented twin.
All quants made using imatrix option, with a calibration corpus rendered through this model's own chat template. The corpus pairs plain prose with tool-calling and reasoning conversations (corpus source data), encoded exactly as this model sees them at inference and processed with --parse-special, so chat-format special tokens contribute to the importance matrix. The corpus rendered for this model is included in this repo: XingChen-AGI_Xing4.0-29B-Intent-calibration-v6.txt. The imatrix is available here: XingChen-AGI_Xing4.0-29B-Intent-imatrix.gguf.
llama.cpp automatically "repacks" weights into an interleaved layout at load time for faster inference on ARM and AVX machines - details in this PR. This once required downloading special Q4_0_4_4/4_8/8_8 files; those are long gone. Online repacking now covers Q4_0, IQ4_NL, and most K-quants, so no special quant choice is needed for CPU inference.
An older (early 2024) but still useful write-up with charts comparing quant performances is provided by Artefact2 here
The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.
If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.
If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.
Hugging Face can also do this math for you: add your hardware in your Local Apps settings and the model page will show which files fit.
Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.
If you don't want to think too much, grab one of the K-quants. These are in format 'QX_K_X', like Q5_K_M.
If you want to get more into the weeds, you can check out this extremely useful feature chart:
But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQX_X, like IQ3_M. These are newer and offer better performance for their size.
These I-quants can also be used on CPU, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.
