Fixes the 11 CodeRabbit findings that survived triage on PR #2240. Two Security/Major items (public-API artifact size guards on :func:`score`; removing target names from logs) were consciously deferred per author call. Documentation ============= * :pr:`comment:3883483129` -- ``docs/.../_onnx_quantization.rst``: ``[expr for i, ex in enumerate(ds) if i < 500]`` doesn't stop the streaming iterator -- Python evaluates every element of ``ds`` against the ``i < 500`` filter, so users copy-pasting the doc drain the full 50k-image ImageNet-1k validation split each time. Replaced with ``itertools.islice(ds, 500)``. * :pr:`comment:3883483137` -- picker examples referenced ``scores`` but the preceding block only defined ``result``; copying the block raised ``NameError``. Added ``scores = result["scores"]`` bridging line. * :pr:`comment:3883483146` -- CLI ``--metric`` help said "activations", but :func:`score` runs both graphs through ORT and compares **graph outputs**. Same imprecision propagated into the ``Metric`` enum docstring and the ``metrics.py`` module docstring. Standardised on "graph outputs" across all three. * :pr:`comment:3883483177` -- ``op_types_scope`` docstring still said unsupported targets are scored ``0.0``; the earlier ``failed``-field rework moved them to a distinct list. Doc now documents the new behavior and the "0.0 means free / ``failed`` means we don't know" distinction. Correctness =========== * :pr:`comment:3883483142` -- ``_render_ranked_table`` printed "no quantizable targets found" whenever ``scores`` was empty, hiding the case where every probe failed. Split into three branches: empty + no failed = "no targets"; empty + failed = "no scores produced; N target(s) failed"; non-empty + failed adds a trailing "N target(s) failed to probe" line. * :pr:`comment:3883483161` -- ``cos_dist`` returned ``1.0`` when both reference and quantized outputs were all-zero (``0 / (0 + _EPS) = 0`` -> distance 1). A probe whose outputs are both zero should score as identical, not maximally sensitive. Guarded with ``np.where(norm > 0, ..., 1.0)`` so ``distance == 0.0``. Added ``test_both_zero_vectors_return_zero_distance`` as a regression witness in ``test_metrics.py``. * :pr:`comment:3883483169` -- :func:`suggest_exclusion` coverage-mode docstring said "largest target set whose cumulative score stays at or below ``coverage * total_mass``", but the implementation is a rank-prefix walker that stops at the first non-fitting target (e.g. ``{a: 4, b: 3, c: 2}`` at ``coverage=0.7`` returns ``[a]`` even though ``{a, c}`` fits with more members). Reworded to describe the actual algorithm and its non-largest-set trade-off. * :pr:`comment:3883483175` -- :func:`summarize_exclusion` skipped unknown ``excluded`` names in ``excluded_mass`` but counted them in ``num_excluded`` / ``num_remaining_quantized``, so ``scores={"a":5,"b":5}`` + ``excluded=["a","unknown"]`` yielded ``num_remaining_quantized == 0`` even though ``b`` remained quantized. Duplicate excluded names skewed the counts too. Filter ``excluded`` to unique names in ``scores`` before counting so all four fields stay consistent. Updated ``test_missing_node_names_default_zero`` (previously pinned the buggy behaviour) and added ``test_duplicate_excluded_names_counted_once``. * :pr:`comment:3883483188` -- ``test_failed_probe_is_recorded`` ``monkeypatch.setattr(score_mod, "quantize", ...)`` targeted the package-level re-exported function object (which ``score_mod`` was bound to via ``from modelopt.onnx.quantization.sensitivity import score``), not the ``modelopt.onnx.quantization.sensitivity.score`` module namespace that :func:`score` actually resolves ``quantize`` from. The fake was never called. Fixed by importing the implementation submodule directly and patching that module's ``quantize`` binding. Also added ``test_failed_probe_records_exceptions`` covering the sibling code path where ``quantize()`` raises rather than silently no-ops. Package structure ================= * :pr:`comment:3883483140` -- ``sensitivity/__init__.py`` converted to the ``from .module import *`` re-export pattern used by ``modelopt/torch/quantization/qtensor/`` and other subpackages, keeping the file-scope ``# ruff: noqa: F405`` and the explicit ``__all__`` public-contract list (same shape as ``modelopt/torch/quantization/utils/__init__.py``). ``picker.py`` gained an ``__all__`` list so its wildcard re-export ships exactly ``suggest_exclusion`` + ``summarize_exclusion``. CLI hardening ============= * :pr:`comment:3883483152` -- directory-mode ``--calibration_data_path`` bypassed size validation entirely, and ``_load_calibration_from_path`` then loaded every ``.npz`` shard under it and concatenated the arrays without per-file or aggregate limits. Added ``_validate_calibration_dir()`` that enforces a per- file cap of ``_CALIB_MAX_SIZE_BYTES`` (4 GiB, same as the file-mode guard) and an aggregate cap of ``_CALIB_DIR_MAX_TOTAL_BYTES`` (16 GiB). Empty directories now raise ``FileNotFoundError``. Logging (partial) ================= * :pr:`comment:3883483182` -- scrubbed the raw ``onnx_path`` from the scan-start log line and moved raw exception text to a ``logger.debug(..., exc_info=True)`` on the ``quantize()`` failure path. The per-probe warning still surfaces the exception **class** and the target name (target names are load-bearing for debugging; callers who want them redacted can filter at the log-handler layer). pyproject.toml ============== Registered the ``slow`` and ``slow_gpu`` markers in ``[tool.pytest.ini_options] markers = [...]`` so ``--strict-markers`` (project default via ``addopts``) doesn't fail collection on ``@pytest.mark.slow`` / ``@pytest.mark.slow_gpu`` decorators. These were already used on the CoAtNet integration tests but the marker declarations had never been included in a shipping commit. Deferred (author call, documented in the review threads) ======================================================== * :pr:`comment:3883483180` -- public-API artifact size guards on :func:`score`. Requires expanding the API contract (raise on legitimately large ONNX inputs OR plumb a trust knob through). Not in scope for this PR. * Target-name scrubbing from log messages -- keeping them is a deliberate debuggability choice. Signed-off-by: gcunhase <4861122+gcunhase@users.noreply.github.com> Co-Authored-By: modelopt-fix-agent-bot (Opus 4.7) <noreply@anthropic.com>
NVIDIA Model Optimizer (referred to as Model Optimizer, or ModelOpt) is a library comprising state-of-the-art model optimization techniques including quantization, pruning, Neural Architecture Search (NAS), distillation, speculative decoding and sparsity to accelerate models.
[Input] Model Optimizer currently supports inputs of a Hugging Face, PyTorch or ONNX model.
[Optimize] Model Optimizer provides Python APIs for users to easily compose the above model optimization techniques and export an optimized quantized checkpoint. Model Optimizer is also integrated with NVIDIA Megatron-Bridge, Megatron-LM and Hugging Face Accelerate for training required inference optimization techniques.
[Export for deployment] Seamlessly integrated within the NVIDIA AI software ecosystem, the quantized checkpoint generated from Model Optimizer is ready for deployment in downstream inference frameworks like SGLang, TensorRT-LLM, TensorRT, or vLLM. The unified Hugging Face export API now supports both transformers and diffusers models.
Latest News
- [2026/08/17] BLOG: Developing Nemotron 3.5 Lightning NVFP4 with QAD Using NVIDIA Model Optimizer: Learn how quantization-aware distillation recovers accuracy from aggressive NVFP4 quantization while reducing model size and increasing throughput.
- [2026/06/26] BLOG: Creating the NVIDIA Nemotron 3 Ultra NVFP4 Checkpoint with NVIDIA Model Optimizer: How we quantized Nemotron 3 Ultra (550B) to NVFP4 with Model Optimizer — up to 5.9× higher decode-heavy inference throughput than GLM-5.1 754B FP4 while matching BF16 accuracy. NVFP4 Checkpoint on Hugging Face.
- [2026/05/27] End-to-end Optimization tutorial for Nemotron-3-Nano-30B-A3B: Pruning + two-phase distillation + FP8 quantization achieving 2.6× vLLM throughput and 2.6× memory reduction.
- [2026/05/13] Puzzletron: A new algorithm for heterogeneous pruning & NAS of LLM and VLM models.
- [2026/04/15] Customer story: Domyn compresses Colosseum-355B → 260B using ModelOpt's Minitron pruning + distillation
- [2026/03/17] Customer story: Bielik.AI builds Bielik Minitron 7B (33% smaller, 50% faster, 90% quality retained) using ModelOpt's Minitron pruning + distillation
- [2026/03/11] Model Optimizer quantized Nemotron-3-Super checkpoints are available on Hugging Face for download: FP8, NVFP4. Learn more in the Nemotron 3 Super release blog. Check out how to quantize Nemotron 3 models for deployment acceleration here
- [2026/03/11] NeMo Megatron Bridge now supports Nemotron-3-Super quantization (PTQ and QAT) and export workflows using the Model Optimizer library. See the Quantization (PTQ and QAT) guide for FP8/NVFP4 quantization and HF export instructions.
- [2025/12/11] BLOG: Top 5 AI Model Optimization Techniques for Faster, Smarter Inference
- [2025/12/08] NVIDIA TensorRT Model Optimizer is now officially rebranded as NVIDIA Model Optimizer.
- [2025/10/07] BLOG: Pruning and Distilling LLMs Using NVIDIA Model Optimizer
- [2025/09/17] BLOG: An Introduction to Speculative Decoding for Reducing Latency in AI Inference
- [2025/09/11] BLOG: How Quantization Aware Training Enables Low-Precision Accuracy Recovery
- [2025/08/29] BLOG: Fine-Tuning gpt-oss for Accuracy and Performance with Quantization Aware Training
- [2025/08/01] BLOG: Optimizing LLMs for Performance and Accuracy with Post-Training Quantization
- [2025/06/24] BLOG: Introducing NVFP4 for Efficient and Accurate Low-Precision Inference
- [2025/05/14] NVIDIA TensorRT Unlocks FP4 Image Generation for NVIDIA Blackwell GeForce RTX 50 Series GPUs
- [2025/04/21] Adobe optimized deployment using Model-Optimizer + TensorRT leading to a 60% reduction in diffusion latency, a 40% reduction in total cost of ownership
- [2025/04/05] NVIDIA Accelerates Inference on Meta Llama 4 Scout and Maverick. Check out how to quantize Llama4 for deployment acceleration here
- [2025/03/18] World's Fastest DeepSeek-R1 Inference with Blackwell FP4 & Increasing Image Generation Efficiency on Blackwell
- [2025/02/25] Model Optimizer quantized NVFP4 models available on Hugging Face for download: DeepSeek-R1-FP4, Llama-3.3-70B-Instruct-FP4, Llama-3.1-405B-Instruct-FP4
- [2025/01/28] Model Optimizer has added support for NVFP4. Check out an example of NVFP4 PTQ here.
- [2025/01/28] Model Optimizer is now open source!
Previous News
- [2024/10/23] Model Optimizer quantized FP8 Llama-3.1 Instruct models available on Hugging Face for download: 8B, 70B, 405B.
- [2024/09/10] Post-Training Quantization of LLMs with NVIDIA NeMo and Model Optimizer.
- [2024/08/28] Boosting Llama 3.1 405B Performance up to 44% with Model Optimizer on NVIDIA H200 GPUs
- [2024/08/28] Up to 1.9X Higher Llama 3.1 Performance with Medusa
- [2024/08/15] New features in recent releases: Cache Diffusion, QLoRA workflow with NVIDIA NeMo, and more. Check out our blog for details.
- [2024/06/03] Model Optimizer now has an experimental feature to deploy to vLLM as part of our effort to support popular deployment frameworks. Check out the workflow here
- [2024/05/08] Announcement: Model Optimizer Now Formally Available to Further Accelerate GenAI Inference Performance
- [2024/03/27] Model Optimizer supercharges TensorRT-LLM to set MLPerf LLM inference records
- [2024/03/18] GTC Session: Optimize Generative AI Inference with Quantization in TensorRT-LLM and TensorRT
- [2024/03/07] Model Optimizer's 8-bit Post-Training Quantization enables TensorRT to accelerate Stable Diffusion to nearly 2x faster
- [2024/02/01] Speed up inference with Model Optimizer quantization techniques in TRT-LLM
Install
To install stable release packages for Model Optimizer with pip from PyPI:
pip install -U nvidia-modelopt[all]
Model Optimizer will download and install additional third-party open source software projects. Review the license terms of these open source projects before use.
To install from source in editable mode with all development dependencies or to use the latest features, run:
# Clone the Model Optimizer repository
git clone git@github.com:NVIDIA/Model-Optimizer.git
cd Model-Optimizer
pip install -e .[dev]
You can also directly use NVIDIA container images, which have Model Optimizer pre-installed:
nvcr.io/nvidia/pytorch:<version>-py3nvcr.io/nvidia/nemo:<version>nvcr.io/nvidia/tensorrt-llm/release:<version>
Before pulling and using the container images, please review their respective license terms. Make sure to upgrade Model Optimizer to the latest version as described above. Visit our installation guide for more fine-grained control on installed dependencies or for alternative docker images and environment variables to setup.
Techniques
| Technique | Description | Examples | Docs |
|---|---|---|---|
| Post Training Quantization | Compress model size by 2x-4x, speeding up inference while preserving model quality! | [HF LLMs / VLMs] [Megatron-Bridge LLMs / VLMs] [Diffusers] [ONNX] [Windows] | [docs] |
| Quantization Aware Training / Distillation | Refine accuracy of quantized models even further with a few training steps! | [Hugging Face] [Megatron-Bridge] | [docs] |
| Pruning | Reduce your model parameters or memory footprint and accelerate inference by removing unnecessary weights! | [General] [Megatron-Bridge] | |
| Distillation | Reduce deployment model size by teaching small models to behave like larger models! | [Hugging Face] [Megatron-Bridge] [Megatron-LM] | [docs] |
| Speculative Decoding | Train draft modules to predict extra tokens during inference! | [Hugging Face] [Megatron-LM] | [docs] |
| Sparsity | Efficiently compress your model by storing only its non-zero parameter values and their locations | [Hugging Face] | [docs] |
Pre-Quantized Checkpoints
- Ready-to-deploy checkpoints [🤗 Hugging Face - Nvidia Model Optimizer Collection]
- Deployable on TensorRT-LLM, vLLM and SGLang
- More models coming soon!
Resources
Model Support Matrix
| Model Type | Support Matrix |
|---|---|
| LLM / VLM Quantization | View Support Matrix |
| Diffusers Quantization | View Support Matrix |
| ONNX Quantization | View Support Matrix |
| Windows Quantization | View Support Matrix |
| Quantization Aware Training | View Support Matrix |
| Pruning | View Support Matrix |
| Distillation | View Support Matrix |
| Speculative Decoding | View Support Matrix |
Deprecation Policy
Model Optimizer follows a structured approach to managing deprecated features:
- Communication: Deprecation notices are documented in the Changelog. Deprecated items include source code statements indicating deprecation timing, with runtime warnings issued upon use.
- Migration Period: Since Model Optimizer is still pre-1.0, we provide a 1-release (~1-month) migration period after deprecation. During this window, deprecated features continue functioning while issuing warnings.
- Scope: The policy addresses both complete deprecations (entire APIs removed) and partial ones (specific parameters removed while methods remain).
- Removal: Following the migration period, deprecated elements are removed in alignment with semantic versioning standards, potentially including breaking changes in minor version updates while Model Optimizer remains in 0.x.
Citation
If you use NVIDIA Model Optimizer in your research, please cite it as follows:
@misc{nvidia-modelopt,
author = {{NVIDIA Corporation}},
title = {{NVIDIA Model Optimizer}},
howpublished = {\url{https://github.com/NVIDIA/Model-Optimizer}},
year = {2024--2026},
note = {GitHub repository}
}
Contributing
Model Optimizer is now open source! We welcome any feedback, feature requests and PRs. Please read our Contributing guidelines for details on how to contribute to this project.
AI Agents
ModelOpt's agent skills can be installed from this repository and used in any workspace.
Claude Code
claude plugin marketplace add https://github.com/NVIDIA/Model-Optimizer.git
claude plugin install modelopt@modelopt
Codex
codex plugin marketplace add https://github.com/NVIDIA/Model-Optimizer.git
Then open /plugins, select the modelopt marketplace, and install modelopt.
Contributors can also use the skills directly from a checkout. See the
agent tooling notes.
Top Contributors
Happy optimizing!
