Llamacpp imatrix Quantizations of Nex-N2.5-Pro by nex-agi

Using llama.cpp release b10896 for quantization.

Original model: https://huggingface.co/nex-agi/Nex-N2.5-Pro

Model details:

  • Parameter count: 397B
  • Input support: text
  • Speculative decoding: no
  • imatrix: yes - details

How to run

Prompt format

<|im_start|>system
{system_prompt}<|im_end|>
<|im_start|>user
{prompt}<|im_end|>
<|im_start|>assistant
<think>

Don't know which to choose? Grab Q4_K_M (250.83GB) - usually a good mix of size and performance. Download instructions available here

Available files:

Filename Quant type File Size Split Description
Nex-N2.5-Pro-Q6_K.gguf Q6_K 349.80GB true Very high quality, near perfect, recommended.
Nex-N2.5-Pro-Q6_K_S.gguf Q6_K_S 333.16GB true Very high quality, near perfect, a little smaller than Q6_K with almost all of the model at Q6_K precision, recommended.
Nex-N2.5-Pro-Q5_K_M.gguf Q5_K_M 305.61GB true High quality, recommended.
Nex-N2.5-Pro-Q5_K_S.gguf Q5_K_S 282.83GB true High quality, recommended.
Nex-N2.5-Pro-Q4_K_M.gguf Q4_K_M 250.83GB true Good quality, default size for most use cases, recommended.
Nex-N2.5-Pro-IQ4_NL.gguf IQ4_NL 249.54GB true Similar to IQ4_XS, but slightly larger.
Nex-N2.5-Pro-Q4_1.gguf Q4_1 249.10GB true Legacy format, similar performance to Q4_K_S but with improved tokens/watt on Apple silicon.
Nex-N2.5-Pro-Q4_K_S.gguf Q4_K_S 233.49GB true Slightly lower quality with more space savings, recommended.
Nex-N2.5-Pro-Q4_0.gguf Q4_0 225.44GB true Legacy format, kept for compatibility with older tools.
Nex-N2.5-Pro-IQ4_XS.gguf IQ4_XS 219.53GB true Decent quality, smaller than Q4_K_S with similar performance, recommended.
Nex-N2.5-Pro-IQ3_M.gguf IQ3_M 209.45GB true Medium-low quality, new method with decent performance comparable to Q3_K_M.
Nex-N2.5-Pro-Q3_K_L.gguf Q3_K_L 200.20GB true Lower quality but usable, good for low RAM availability.
Nex-N2.5-Pro-Q3_K_M.gguf Q3_K_M 189.95GB true Low quality.
Nex-N2.5-Pro-Q3_K_S.gguf Q3_K_S 180.04GB true Low quality, not recommended.
Nex-N2.5-Pro-IQ3_XS.gguf IQ3_XS 178.10GB true Lower quality, new method with decent performance, slightly better than Q3_K_S.
Nex-N2.5-Pro-IQ3_XXS.gguf IQ3_XXS 169.55GB true Lower quality, new method with decent performance, comparable to Q3 quants.
Nex-N2.5-Pro-Q2_K.gguf Q2_K 150.75GB true Very low quality but surprisingly usable.
Nex-N2.5-Pro-IQ2_M.gguf IQ2_M 142.32GB true Relatively low quality, uses SOTA techniques to be surprisingly usable.
Nex-N2.5-Pro-IQ2_S.gguf IQ2_S 127.82GB true Low quality, uses SOTA techniques to be usable.
Nex-N2.5-Pro-IQ2_XS.gguf IQ2_XS 121.42GB true Low quality, uses SOTA techniques to be usable.
Nex-N2.5-Pro-IQ2_XXS.gguf IQ2_XXS 115.09GB true Very low quality, uses SOTA techniques to be usable.
Nex-N2.5-Pro-IQ1_M.gguf IQ1_M 98.08GB true Extremely low quality, not recommended.
Nex-N2.5-Pro-IQ1_S.gguf IQ1_S 87.87GB true Extremely low quality, not recommended.

Download a specific file:

hf download bartowski/Nex-N2.5-Pro-GGUF --include "Nex-N2.5-Pro-Q4_K_M/*" --local-dir ./

Downloading using the Hugging Face CLI

Click to view download instructions

First, make sure you have the Hugging Face CLI installed:

pip install -U "huggingface_hub[cli]"

Download a specific file:

hf download bartowski/Nex-N2.5-Pro-GGUF --include "Nex-N2.5-Pro-Q4_K_M/*" --local-dir ./

The files marked true in the Split column above are stored as multiple parts in a folder. To download all the parts to a local folder, run:

hf download bartowski/Nex-N2.5-Pro-GGUF --include "Nex-N2.5-Pro-Q6_K/*" --local-dir ./

You can either specify a new local-dir (Nex-N2.5-Pro-Q6_K) or download them all in place (./)

How to run

These quants run with llama.cpp - installable in one line via llama.app:

curl -LsSf https://llama.app/install.sh | sh
llama-server -hf bartowski/Nex-N2.5-Pro-GGUF:Q4_K_M

llama-server includes a built-in chat web UI, served at http://localhost:8080 by default.

These quants were made with llama.cpp release b10896 - if this model's architecture is newly supported, you'll need that release or newer to run them.

They also work in: LM Studio · koboldcpp · ramalama · Jan AI · Text Generation Web UI · LoLLMs · Atomic Chat

Per-tensor layouts

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-61746c35382fd0e6 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.83×, Q3_K_M 0.76× and IQ1_S 0.80× 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 349.80GB 7.04 7.05 70 %
Q6_K_S 333.16GB 6.71 6.72 91 %
Q5_K_M 305.61GB 6.15 6.16 70 %
Q5_K_S 282.83GB 5.68 5.70 90 %
Q4_K_M 250.83GB 5.04 5.06 70 %
IQ4_NL 249.54GB 5.01 5.03 70 %
Q4_K_S 233.49GB 4.68 4.71 90 %
IQ4_XS 219.53GB 4.40 4.43 90 %
IQ3_M 209.45GB 4.20 4.22 50 %
Q3_K_L 200.20GB 4.01 4.04 50 %
Q3_K_M 189.95GB 3.80 3.83 70 %
Q3_K_S 180.04GB 3.60 3.63 90 %
IQ3_XS 178.10GB 3.56 3.59 90 %
IQ3_XXS 169.55GB 3.38 3.42 70 %
Q2_K 150.75GB 3.00 3.04 70 %
IQ2_M 142.32GB 2.83 2.87 70 %
IQ2_S 127.82GB 2.54 2.58 70 %
IQ2_XS 121.42GB 2.41 2.45 90 %
IQ2_XXS 115.09GB 2.28 2.32 70 %
IQ1_M 98.08GB 1.93 1.98 70 %
IQ1_S 87.87GB 1.73 1.77 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.0285 ± 0.0005 0.0396 ± 0.0007 0.83× +3.7 %
Q3_K_M 0.0700 ± 0.0012 0.1063 ± 0.0017 0.76× +4.7 %
IQ1_S 0.5358 ± 0.0063 0.7574 ± 0.0077 0.80× +7.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.

imatrix

All quants made using imatrix option with dataset from here. The imatrix is available here: Nex-N2.5-Pro-imatrix.gguf.

ARM/AVX information

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.

Which file should I choose?

Click here for details

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:

llama.cpp feature matrix

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.

Credits

Thank you kalomaze and Dampf for assistance in creating the imatrix calibration dataset.

Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski

Downloads last month
1,979
GGUF
Model size
396B params
Architecture
qwen35moe
Hardware compatibility
Log In to add your hardware

1-bit

2-bit

3-bit

4-bit

5-bit

6-bit

8-bit

Inference Providers NEW
This model isn't deployed by any Inference Provider. 🙋 Ask for provider support

Model tree for bartowski/Nex-N2.5-Pro-GGUF

Quantized
(4)
this model

Collections including bartowski/Nex-N2.5-Pro-GGUF