MiniCPM5-2B-GGUF

Experimental global target bits‑per‑weight quantization of openbmb/MiniCPM5-2B

Using non-standard (forked) LLaMA C++ release b11529 for quantization.

Original model: openbmb/MiniCPM5-2B

From the original model creators:

Highlights

We are releasing MiniCPM5-2B, the second model in the MiniCPM5 series, following MiniCPM5-1B. It is a dense 2B Transformer that scales up the same training recipe, built for on-device, local deployment, and resource-constrained scenarios, reaching 2B-class open-source SOTA.

🏆 2B-class open-source SOTA: compared with strong open-source models of similar size, MiniCPM5-2B achieves SOTA performance within this comparison set. It remains competitive with 4B-class models overall, while showing its advantages over models of comparable size in coding, mathematics, long-context understanding, tool use, and agentic tasks.

<div id="capability-comparison-radar" class="radar-visual" role="img" aria-label="Capability radar chart comparing MiniCPM5-2B with 4B-class models. Each axis is normalized independently to 100 percent."> <style> #capability-comparison-radar { --foreground: #171717; display: block; width: 100%; max-width: 620px; margin: 0 auto; background: #fff; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "PingFang SC", "Hiragino Sans GB", "Microsoft YaHei", sans-serif; } #capability-comparison-radar svg { display: block; width: 100%; height: auto; background: #fff; } #capability-comparison-radar .title { fill: var(--foreground); font-size: 16px; font-weight: 600; letter-spacing: 0; } #capability-comparison-radar .axis-label { fill: #333; font-size: 12px; font-weight: 600; } #capability-comparison-radar .ring { fill: none; stroke: rgba(128,128,128,.18); stroke-width: .8; } #capability-comparison-radar .spoke { stroke: rgba(128,128,128,.25); stroke-width: .8; } #capability-comparison-radar .ring-label { fill: #8a8a8a; font-size: 9px; } #capability-comparison-radar .series { stroke-linejoin: round; } #capability-comparison-radar .series.primary { stroke-width: 2.4; } #capability-comparison-radar .legend-label { fill: #171717; font-size: 12px; font-weight: 600; } #capability-comparison-radar .legend-average { fill: #666; font-size: 11px; } #capability-comparison-radar .legend-swatch { rx: 3; } @media (max-width: 900px) { #capability-comparison-radar { overflow-x: auto; } #capability-comparison-radar svg { min-width: 620px; } } </style> <svg viewBox="0 0 680 560" aria-hidden="true"> <g transform="translate(-20 0)"> <text x="40" y="28" class="title" text-anchor="start">Capability Radar by Dimension</text> <polygon points="340.0,235.0 362.5,243.2 374.5,263.9 370.3,287.5 352.0,302.9 328.0,302.9 309.7,287.5 305.5,263.9 317.5,243.2" class="ring" stroke="rgba(128,128,128,.18)" stroke-width=".8"/> <text x="344.0" y="238.0" class="ring-label">20%</text> <polygon points="340.0,200.0 385.0,216.4 408.9,257.8 400.6,305.0 363.9,335.8 316.1,335.8 279.4,305.0 271.1,257.8 295.0,216.4" class="ring" stroke="rgba(128,128,128,.18)" stroke-width=".8"/> <text x="344.0" y="203.0" class="ring-label">40%</text> <polygon points="340.0,165.0 407.5,189.6 443.4,251.8 430.9,322.5 375.9,368.7 304.1,368.7 249.1,322.5 236.6,251.8 272.5,189.6" class="ring" stroke="rgba(128,128,128,.18)" stroke-width=".8"/> <text x="344.0" y="168.0" class="ring-label">60%</text> <polygon points="340.0,130.0 430.0,162.8 477.9,245.7 461.2,340.0 387.9,401.6 292.1,401.6 218.8,340.0 202.1,245.7 250.0,162.8" class="ring" stroke="rgba(128,128,128,.18)" stroke-width=".8"/> <text x="344.0" y="133.0" class="ring-label">80%</text> <polygon points="340.0,95.0 452.5,135.9 512.3,239.6 491.6,357.5 399.9,434.4 280.1,434.4 188.4,357.5 167.7,239.6 227.5,135.9" class="ring" stroke="rgba(29,111,208,.28)" stroke-width="1"/> <text x="344.0" y="98.0" class="ring-label">100%</text> <line x1="340" y1="270" x2="340.0" y2="95.0" class="spoke"/> <text x="340.0" y="63.5" class="axis-label" text-anchor="middle">Code Reasoning</text> <line x1="340" y1="270" x2="452.5" y2="135.9" class="spoke"/> <text x="472.7" y="111.8" class="axis-label" text-anchor="start">Math Reasoning</text> <line x1="340" y1="270" x2="512.3" y2="239.6" class="spoke"/> <text x="543.4" y="234.1" class="axis-label" text-anchor="start">Instruction Following</text> <line x1="340" y1="270" x2="491.6" y2="357.5" class="spoke"/> <text x="518.8" y="373.2" class="axis-label" text-anchor="start">General Knowledge</text> <line x1="340" y1="270" x2="399.9" y2="434.4" class="spoke"/> <text x="410.6" y="464.0" class="axis-label" text-anchor="start">Long Context</text> <line x1="340" y1="270" x2="280.1" y2="434.4" class="spoke"/> <text x="269.4" y="464.0" class="axis-label" text-anchor="end">Tool Use</text> <line x1="340" y1="270" x2="188.4" y2="357.5" class="spoke"/> <text x="161.2" y="373.3" class="axis-label" text-anchor="end">Coding Agent</text> <line x1="340" y1="270" x2="167.7" y2="239.6" class="spoke"/> <text x="136.6" y="234.1" class="axis-label" text-anchor="end">Search Agent</text> <line x1="340" y1="270" x2="227.5" y2="135.9" class="spoke"/> <text x="207.3" y="111.8" class="axis-label" text-anchor="end">General Agent</text> <polygon points="340.0,136.7 450.1,138.8 498.4,242.1 491.6,357.5 398.4,430.3 289.5,408.8 188.4,357.5 188.2,243.2 249.3,161.9" class="series" fill="#E85D4C" fill-opacity=".10" stroke="#E85D4C" stroke-width="1.5"/> <circle cx="340.0" cy="136.7" r="3" fill="#E85D4C"/> <circle cx="450.1" cy="138.8" r="3" fill="#E85D4C"/> <circle cx="498.4" cy="242.1" r="3" fill="#E85D4C"/> <circle cx="491.6" cy="357.5" r="3" fill="#E85D4C"/> <circle cx="398.4" cy="430.3" r="3" fill="#E85D4C"/> <circle cx="289.5" cy="408.8" r="3" fill="#E85D4C"/> <circle cx="188.4" cy="357.5" r="3" fill="#E85D4C"/> <circle cx="188.2" cy="243.2" r="3" fill="#E85D4C"/> <circle cx="249.3" cy="161.9" r="3" fill="#E85D4C"/> <polygon points="340.0,134.4 448.9,140.2 512.3,239.6 462.2,340.5 367.8,346.5 308.0,358.0 231.0,332.9 242.3,252.8 250.1,162.9" class="series" fill="#2A9D8F" fill-opacity=".10" stroke="#2A9D8F" stroke-width="1.5"/> <circle cx="340.0" cy="134.4" r="3" fill="#2A9D8F"/> <circle cx="448.9" cy="140.2" r="3" fill="#2A9D8F"/> <circle cx="512.3" cy="239.6" r="3" fill="#2A9D8F"/> <circle cx="462.2" cy="340.5" r="3" fill="#2A9D8F"/> <circle cx="367.8" cy="346.5" r="3" fill="#2A9D8F"/> <circle cx="308.0" cy="358.0" r="3" fill="#2A9D8F"/> <circle cx="231.0" cy="332.9" r="3" fill="#2A9D8F"/> <circle cx="242.3" cy="252.8" r="3" fill="#2A9D8F"/> <circle cx="250.1" cy="162.9" r="3" fill="#2A9D8F"/> <polygon points="340.0,189.3 411.4,184.9 502.9,241.3 455.3,336.6 356.7,315.9 288.5,411.4 320.8,281.1 266.8,257.1 298.8,220.9" class="series" fill="#E09F3E" fill-opacity=".10" stroke="#E09F3E" stroke-width="1.5"/> <circle cx="340.0" cy="189.3" r="3" fill="#E09F3E"/> <circle cx="411.4" cy="184.9" r="3" fill="#E09F3E"/> <circle cx="502.9" cy="241.3" r="3" fill="#E09F3E"/> <circle cx="455.3" cy="336.6" r="3" fill="#E09F3E"/> <circle cx="356.7" cy="315.9" r="3" fill="#E09F3E"/> <circle cx="288.5" cy="411.4" r="3" fill="#E09F3E"/> <circle cx="320.8" cy="281.1" r="3" fill="#E09F3E"/> <circle cx="266.8" cy="257.1" r="3" fill="#E09F3E"/> <circle cx="298.8" cy="220.9" r="3" fill="#E09F3E"/> <polygon points="340.0,95.0 452.5,135.9 499.8,241.8 476.2,348.7 399.9,434.4 280.1,434.4 220.0,339.3 167.7,239.6 227.5,135.9" class="series primary" fill="#1D6FD0" fill-opacity=".22" stroke="#1D6FD0" stroke-width="2.4"/> <circle cx="340.0" cy="95.0" r="3" fill="#1D6FD0"/> <circle cx="452.5" cy="135.9" r="3" fill="#1D6FD0"/> <circle cx="499.8" cy="241.8" r="3" fill="#1D6FD0"/> <circle cx="476.2" cy="348.7" r="3" fill="#1D6FD0"/> <circle cx="399.9" cy="434.4" r="3" fill="#1D6FD0"/> <circle cx="280.1" cy="434.4" r="3" fill="#1D6FD0"/> <circle cx="220.0" cy="339.3" r="3" fill="#1D6FD0"/> <circle cx="167.7" cy="239.6" r="3" fill="#1D6FD0"/> <circle cx="227.5" cy="135.9" r="3" fill="#1D6FD0"/> <rect x="40" y="490" width="18" height="18" class="legend-swatch" fill="#1D6FD0"/> <text x="66" y="504" class="legend-label">MiniCPM5-2B</text> <text x="66" y="520" class="legend-average">avg 53.9</text> <rect x="195" y="490" width="18" height="18" class="legend-swatch" fill="#E85D4C"/> <text x="221" y="504" class="legend-label">Qwen3.5-4B</text> <text x="221" y="520" class="legend-average">avg 51.1</text> <rect x="350" y="490" width="18" height="18" class="legend-swatch" fill="#2A9D8F"/> <text x="376" y="504" class="legend-label">granite-4.2-3B</text> <text x="376" y="520" class="legend-average">avg 42.7</text> <rect x="505" y="490" width="18" height="18" class="legend-swatch" fill="#E09F3E"/> <text x="531" y="504" class="legend-label">LFM2.5-2.6B</text> <text x="531" y="520" class="legend-average">avg 33.2</text> <text x="340" y="548" class="legend-average" text-anchor="middle">each axis: max = 100%</text> </g> </svg> </div>

---

⚠️ PLEASE READ THIS BEFORE USING THESE EXPERIMENTAL VERSIONS! ⚠️

An area of personal interest is finding ways to optimize the inference performance of LLMs when deployed in resource-constrained environments like commodity hardware, desktops, laptops, mobiles, edge devices, etc. There are many approaches to accomplish this, including architecture simplification and knowledge distillation, but my focus has been primarily on quantization and pruning.

The method to produce these experimental versions involves using a custom version of llama-imatrix to generate an imatrix that includes tensor statistics, and a custom version of llama-quantize, which computes a per-tensor quantization error, to automatically select the lowest error quantization recipe that achieves a global target bits‑per‑weight (bpw). More details on the implementation and test results here

There are two pull requests (#14891 & #15550) to merge these changes back into the core llama.cpp project. This may or may not ever happen so, until then, the modified versions will be available on GitHub.

For testing and comparison, I use models produced by Bartowski (see credits below) and Unsloth (Daniel and Michael Han do some really interesting stuff!) but when they don't provide versions of the required model, tests and comparisons are against standard quantization obtained by simply running llama-quantize with no further optimizations.

All experimental versions were generated using an appropriate imatrix created from datasets available at eaddario/imatrix-calibration. In llama.cpp, an imatrix is a calibration file derived from running representative text through the model and collecting activation statistics. It is used to weight quantization error so that error in more “important” directions (as estimated from activations) is penalized more heavily.

The process to generate these models is roughly as follows:

1. Convert the original model's safetensors to GGUF F16
2. Estimate the Perplexity score for the F16 model (baseline) using the wikitext-2-raw-v1 dataset, and save the logits
3. Generate an imatrix from the most appropriate calibration dataset
4. Quantize the baseline model targeting a bpw average (e.g. llama-quantize --target-bpw 4.5678 --state-file --imatrix imatrix.gguf baseline-model-F16.gguf 12)
5. Calculate Perplexity, KL Divergence, ARC (Easy+Challenge), GPQA-Diamond, HellaSwag, MMLU-Redux, Truthful QA and WinoGrande scores for each quantized model
6. Keep version with the best 𝜌PPL and μKLD scores
7. Repeat until all desired quants are created

Misconceptions about BF16 to F16 Conversion

A common concern when converting BFloat16 (BF16) models to Float16 (F16) is the potential for accuracy loss. Specifically:

• Weight Clipping (Overflow): Clipping, or overflow, is often feared but only occurs if a model's weights exceed the range of ±65,503. This is a relatively rare issue in practice.
• Subnormal Zeroing (Underflow): A more frequent occurrence is underflow, where weights smaller than approximately 5.96x10⁻⁸ are converted to zero.

Crucially, when the F16 model is subsequently used for quantization, the resulting degradation in metrics like Perplexity (PPL) or Kullback–Leibler Divergence (KLD) is minimal. Any variations are typically restricted to the hundreds or thousandths decimal places compared to the BF16 model.

However, considering that weight clipping presents a more substantial risk to model integrity, every BF16 base model undergoes validation prior to the conversion process. Consequently, no models hosted in this repository exhibit performance degradation due to overflow clipping.

While BF16 offers precision benefits, performance remains a key factor.

• Conversion Speed: Tests, such as timing convert_hf_to_gguf.py, show a notable performance difference, with conversion to BF16 being 15–30% slower than to F16.
• Inference Speed: A less pronounced but still present difference (3–6%) is observed during inference. Although native BF support has been introduced by many chip manufacturers, the slower performance may stem from the entire software and hardware stack (firmware, libraries, etc.) not being fully optimized yet.

The choice to prioritize F16 over BF16 is driven by a focus on maximizing performance in specific deployment environments. My primary objective is not large-scale quantization production, a domain where others like Bartowski and Unsloth excel at, but rather optimizing inference performance for resource-constrained environments. Since BF16 support is not yet widespread in areas like mobile, edge, and embedded devices, using F16 ensures broader compatibility and easier optimization for these use cases.

Advantages and disadvantages of the global target bits‑per‑weight quantization process

Advantages

1. Target arbitrary size models

   • When specifying --target-bpw 4.5678 for instance, the algorithm will produce a model (nearly) exactly of that size, which is very useful for maximizing VRAM usage. In a system with 24GB VRAM and a 70B model, standard quants might produce a 16.8GB file (too small, quality left on table) or a 24.1GB file (won't fit). This approach can generate a 23.85GB file to utilize the hardware fully.

2. Data-driven mixed precision often can improve quality at fixed size

   • Instead of using hardcoded heuristics (e.g. make attn_v Q5_K for a 70B model), that may be sub‑optimal for a given architecture or size, the quantization mix is determined by the actual error sensitivity of the specific model's weights. This, in practice, often yields a better quality/size trade-off, especially in aggressive quantization scenarios (1.5 to 3.5 bpw), or for unusual architectures.

   • Please note: llama.cpp’s heuristics have been tuned across many models and are highly optimized; although the target bpw method produces better quality often (>75% based on tests with 130 models from 11 different families), it can also lose in surprising cases.

3. Allows better like-for-like comparisons between models and families

   • Standard llama.cpp quantization uses hardcoded rules like: "use Q4_K_M, except bump some tensors up/down, except fall back if incompatible, except keep some tensors unquantized..." and for that reason, two different models quantized with the same Q4_K_M type can end up with very different bpw (e.g. 4.75 and 4.30).

   • All things being equal, the performance of a model is usually proportional to its overall bpw size; models with a higher bpw tend to perform better than lower bpw models. Since model A has simply been given more bits, it will typically perform better (lower perplexity, better eval scores, etc.) even if the underlying quantization method is identical. That makes comparing the performance not a controlled experiment, because the comparison is between models with different effective compression ratios.

   • --target-bpw tries to address that by making the experiment more controlled: each model gets quantized to land on (approximately) the same global byte budget, so that the models' performance differences are more attributable to architecture/training differences, quantization error behaviour at the same compression ratio, optimizer’s allocation decisions, etc.

Disadvantages

1. Quantization process is significantly slower than standard

   • This approach can take 5x-10x longer as it quantizes a sample of most tensors into 15 different formats, dequantizes them back to floats, computes error diffs, and selects the best size/error option that fits the global bpw budget.

   • However, the --state-file option will save/use the above-mentioned computations so that future quantizations, for the same model, can be generated at normal speed. It also allows to interrupt the computation process and resume it at a later time.

2. The optimization target is only a proxy for the model's performance quality

   • The process minimizes a per-tensor estimated error computed from sampled rows, not actual perplexity or divergence of output distributions (a future version may address this). Since errors interact nonlinearly across layers, there are no guarantees it will select the best possible quantization recipe subject to the bpw size constraint.

3. An imatrix with activations data is required for best results

   • Activation data is required to compute the bias factor (i.e. the systematic error projected onto activation directions). If the imatrix file does not contain activation data, the --target-bpw option will refuse to run.

---

Models

Bits per weight, size, perplexity and KL Divergence scores

ARC, GPQA-Diamond, HellaSwag, MMLU-Redux, Truthful QA, and WinoGrande scores

Scores generated using llama-perplexity with 750 tasks per test where possible, and a context size of 1024 tokens.

For the test data used in the generation of these scores, follow the appropriate links: ARC Challenge, Truthful QA, GPQA-Diamond, HellaSwag, MMLU-Redux, WinoGrande

Tokens per second benchmarks

Scores generated using llama-bench. Standard (llama-quantize with no optimization) Q4_K_M quantization included for comparison.

Metrics used

Perplexity: one of the key metrics used in NLP evaluation. It measures the quality of a language model by evaluating how well it predicts the next token given a particular sequence of words. A PPL of 1 indicates an exact match between predicted and actual, whereas values greater than one indicate a degree of "surprise" the generated token differs from the expected.

Kullback–Leibler (KL) Divergence: a statistical measure of how much a probability distribution differs from another. When quantizing models (or altering the original tensors in any way for that matter), the closest we can preserve the weights' probability distribution to the original model the better, thus the closest to 0 the better.

AI2 Reasoning Challenge (ARC): a benchmark to evaluate the ability of AI models to answer complex science questions that require logical reasoning beyond pattern matching.

GPQA-Diamond: a challenging dataset of 448 multiple-choice questions written by domain experts in biology, physics, and chemistry.

HellaSwag: the Harder Endings, Longer contexts, and Low-shot Activities for Situations With Adversarial Generations (bit of a mouthful!) is a benchmark designed to test commonsense natural language inference. It requires the model to predict the most likely ending of a sentence.

MMLU: the Massive Multitask Language Understanding evaluates LLMs’ general knowledge and problem-solving abilities across 57 subjects, including elementary mathematics, US history, computer science, and law.

Truthful QA: evaluates how well LLMs generate truthful responses to questions. It identifies whether AI models can avoid generating false or misleading information, particularly in areas where human knowledge is prone to misconceptions.

Winogrande: based on the Winograd Schema Challenge, is a natural language understanding task requiring models to resolve ambiguities in sentences involving pronoun references.

Credits

LLaMa C++ has a large and vibrant community of contributors (~1,600 last time I checked) that actively maintain and extend its functionality, adding new models and architectures almost as fast as they appear. Considering the breakneck speed at which the AI/ML field is advancing, this alone is a remarkable feat!

While I'm grateful to all contributors, I want to recognise three in particular:

• Colin Kealty (Bartowski), for the many contributions and for being one of the best sources of high quality quantized models available on Hugging Face
• Georgi Gerganov for his amazing work with llama.cpp and the ggml/gguf libraries
• Iwan Kawrakow for being one of the key authors behind the many quantization algorithms and the imatrix functionality.