### What does this PR do? Type of change: Bug fix + CI / infra torch 2.13 + torchvision 0.28 were published to PyPI on 2026-07-08 and broke the `onnx (torch_trt)` example job (which had passed the day before). This PR fixes that break and hardens CI against the next one: 1. **Fix `torch_trt` (torch/torchvision/torch-tensorrt trio pin).** The base install pulled torch 2.13 / torchvision 0.28, then `torch-tensorrt 2.12.1` downgraded torch back to 2.12 but left torchvision at 0.28 (which pins `torch==2.13`) — breaking `import`. `examples/torch_trt/requirements.txt` now caps `torch-tensorrt>=2.4.0,<2.13` + `torchvision<0.28` so the trio stays consistent (also protects direct `pip install -r` users). 2. **Unit tests default to torch 2.13.** `noxfile.py` gains `torch_213` (`torchvision~=0.28.0`); the required `linux`/`windows` jobs and the multi-version Python spread (3.10/3.11/3.13/3.14) now run torch 2.13, with torch 2.8–2.12 kept as back-compat legs on Python 3.12. 3. **Per-example allow-failure escape hatch.** `_example_tests_runner.yml` gains an `allow_failure` input; when set, a **test-run** failure is surfaced as a `::warning::` via `continue-on-error` instead of blocking the PR. `example_tests.yml` derives it per example from the repo variable **`ALLOW_FAILURE_EXAMPLE_TESTS`** (comma-separated example names, comma-wrapped so `onnx` ≠ `torch_onnx`). Future breakages can be quarantined by updating the variable — no code change / PR required. ### Testing - Ran the new default unit session locally in an isolated uv venv (torch **2.13.0**+cu130, torchvision **0.28.0**+cu130, transformers **5.12.1**): ``` nox -s "unit-3.12(torch_213, tf_latest)" => 2813 passed, 15 skipped, 1786 warnings in 250.37s ``` - Verified the allow-failure hatch: with `ALLOW_FAILURE_EXAMPLE_TESTS=torch_trt`, the (previously failing) `torch_trt` job reports success with a warning and does not block the required example check. `vars` is re-read on each job attempt, so "Re-run failed jobs" picks up the variable without a fresh trigger. ### Before your PR is "*Ready for review*" - Is this change backward compatible?: ✅ (CI-only; older torch versions still covered) - If you copied code from any other sources or added a new PIP dependency: N/A (no new dependency; only version caps) - Did you write any new necessary tests?: N/A (CI configuration change) - Did you update Changelog?: N/A (CI infra, no user-facing API change) - Did you get Claude approval on this PR?: ❌ (pending — will run `/claude review`) ### Additional Information The `ALLOW_FAILURE_EXAMPLE_TESTS` repo variable can be cleared for `torch_trt` now that the requirements pin lands the real fix; keep it as the standing escape hatch for future example breakages. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Example test jobs can now be configured to “allow failure” without failing the workflow; when enabled, a warning annotation is emitted. * **Bug Fixes** * CI unit-test and GPU-test configurations were refreshed (including a reduced timeout for the `gpu_megatron` job). * **Tests** * Updated unit-test coverage to use the newest Torch 2.13-based setup by default, with back-compat retained where applicable. * **Documentation** * Added inline guidance for how the allow-failure examples list is specified. * **Chores** * Refreshed `torch_trt` example dependency constraints to improve compatibility. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Keval Morabia <28916987+kevalmorabia97@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Torch-TensorRT Quantization
Torch-TensorRT compiles a PyTorch model into an optimized TensorRT engine with no separate export or runtime. This example quantizes a PyTorch / HuggingFace model with NVIDIA Model Optimizer and then compiles the quantized graph in-framework with Torch-TensorRT for deployment.
Quantization is an effective model optimization technique that compresses your models. Model Optimizer inserts Q/DQ nodes into the eager PyTorch graph; torch_tensorrt.compile(ir="dynamo") then converts those Q/DQ nodes into native TensorRT FP8 precision layers, following the Torch-TensorRT quantization guide.
This section focuses on the in-framework Torch-TensorRT path: a PyTorch front end (mtq.quantize) feeding a Dynamo-compiled TensorRT engine, demonstrated end-to-end on a HuggingFace ViT image classifier. If you instead want a portable ONNX → TensorRT artifact, or you start from an ONNX model, see the sibling torch_onnx and onnx_ptq examples (compared in the Support Matrix).
| Section | Description | Link | Docs |
|---|---|---|---|
| Pre-Requisites | Required packages and installation | [Link] | |
| Getting Started | Quantize and compile a ViT in a few lines | [Link] | [docs] |
| Support Matrix | How this path compares to the ONNX examples | [Link] | |
| ViT Recipes | The FP8 recipe shipped with the example | [Link] | |
| Usage | CLI flags for the quantize and accuracy scripts | [Link] | |
| Evaluate Accuracy | Measure ImageNet top-1 / top-5 accuracy | [Link] | |
| Custom Recipes | Plug in your own recipe / model | [Link] | |
| Resources | Roadmap, docs, benchmarks, and support | [Link] |
Pre-Requisites
Docker
Please use the TensorRT docker image (e.g., nvcr.io/nvidia/tensorrt:26.02-py3) or visit our installation docs for more information.
docker run --gpus all -it --rm -v $(pwd):/workspace -w /workspace nvcr.io/nvidia/tensorrt:26.02-py3 bash
Also follow the installation steps below to upgrade to the latest version of Model Optimizer and install example-specific dependencies.
Local Installation
pip install -U "nvidia-modelopt[hf]"
pip install -r requirements.txt
Hardware Requirements
The low-precision kernels Torch-TensorRT emits need a GPU that supports the target format:
| Recipe | Minimum GPU |
|---|---|
fp8 |
Ada / Hopper — compute capability 8.9+ |
Note
Older GPUs still let
mtq.quantizesucceed — it emits fake-quant nodes in PyTorch — buttorch_tensorrt.compilewill not find a real low-precision kernel for an unsupported format.
Getting Started
Quantize a HuggingFace ViT, then compile the Q/DQ graph with Torch-TensorRT into a single torch.nn.Module you call from PyTorch:
import torch
import torch_tensorrt
import modelopt.torch.quantization as mtq
from modelopt.recipe import load_recipe
from modelopt.torch.quantization.utils import export_torch_mode
# 1. Quantize the eager PyTorch model with a Model Optimizer PTQ recipe.
recipe = load_recipe("huggingface/vit/ptq/fp8")
mtq.quantize(model, recipe.quantize.model_dump(), forward_loop=calibrate)
# 2. Compile the quantized (Q/DQ) graph with Torch-TensorRT.
# export_torch_mode() makes Model Optimizer emit Q/DQ in the TRT-friendly form,
# and min_block_size=1 lets single-node Q/DQ + matmul subgraphs become TRT
# precision layers (per the Torch-TensorRT quantization guide).
with export_torch_mode():
trt_model = torch_tensorrt.compile(
model,
ir="dynamo",
min_block_size=1,
truncate_double=True,
inputs=[torch_tensorrt.Input(
min_shape=(1, 3, 224, 224),
opt_shape=(128, 3, 224, 224),
max_shape=(1024, 3, 224, 224),
dtype=torch.float16,
)],
)
logits = trt_model(pixel_values) # call it like any nn.Module
The runnable script torch_tensorrt_ptq.py wraps this flow end-to-end. It:
- Loads a HuggingFace ViT classifier (default
google/vit-large-patch16-224). - Builds a tiny calibration loader from
zh-plus/tiny-imagenet(avoids the gatedILSVRC/imagenet-1krepo, so the example runs unauthenticated). - Runs
mtq.quantizewith one of the recipes undermodelopt_recipes/(see ViT Recipes). - Saves the quantized Model Optimizer state (FP16 weights + Q/DQ metadata) to
<save_dir>/vit_modelopt_state.ptfor reuse without recalibration (see Custom Recipes). - Compiles the quantized model with
torch_tensorrt.compileand verifies that the compiled-model argmax matches the fake-quant argmax on a sample input.
# Default model is google/vit-large-patch16-224, default recipe is the ViT FP8 recipe.
python torch_tensorrt_ptq.py --calib_samples 1024 --batch_size 128
# Quantize but don't TRT-compile (handy on a non-TRT host).
python torch_tensorrt_ptq.py --skip_trt
Note
Both
torch_tensorrt_ptq.pyand the accuracy script (torch_tensorrt_accuracy.py) run the model infloat16.
Support Matrix
All three of these examples reach the same destination — a low-precision TensorRT engine — but quantize at a different point in the pipeline and emit a different artifact, so they suit different deployment stacks:
| Torch-TensorRT (this example) | torch_onnx |
onnx_ptq |
|
|---|---|---|---|
| Starting point | a PyTorch / HF model | a PyTorch / timm model | an already-exported ONNX model |
| Quantize on | the eager PyTorch graph (mtq.quantize) |
the eager PyTorch graph (mtq.quantize) |
the ONNX graph directly (ONNX PTQ) |
| Export step | none — the FX/Dynamo graph stays in-process | torch.onnx.export of the Q/DQ graph, postprocessed for TRT |
none — Q/DQ inserted straight into the ONNX graph |
| Intermediate artifact | none | a Q/DQ ONNX file | a Q/DQ ONNX file |
| Compiler + runtime | torch_tensorrt.compile(ir="dynamo") → a torch.nn.Module you call from PyTorch |
TensorRT builds a standalone engine from the ONNX | TensorRT builds a standalone engine from the ONNX |
| Best when | PyTorch-native serving; you want a drop-in compiled module | you quantize in PyTorch but deploy via a portable ONNX → TRT engine | you only have an ONNX model and never touch PyTorch |
This example and torch_onnx share the same PyTorch front end (mtq.quantize), so the numerics are identical — they differ only in the back end: this one keeps the graph in-process and hands it to Torch-TensorRT, while torch_onnx exports a portable ONNX artifact for the standalone TensorRT runtime. onnx_ptq instead quantizes the ONNX graph directly, for when you start from an ONNX model rather than PyTorch. Pick this example when your serving stack is PyTorch-native and you'd rather avoid an ONNX export step.
ViT Recipes
This is the recipe the CLI selects by default when --model_id points at a HF ViT classifier. It is tuned for the HF ViT module layout and is composed from the shared $import building blocks under modelopt_recipes/configs/ (ptq/units/{w8a8_fp8_fp8,attention_qkv_fp8}) rather than spelling out each quant_cfg entry.
--recipe value |
Calibration | What it quantizes |
|---|---|---|
huggingface/vit/ptq/fp8 (default) |
max |
Per-tensor FP8 (E4M3) on every weight + input quantizer matched by the *weight_quantizer / *input_quantizer globs — encoder Linears, the patch-embed nn.Conv2d projection, and the classifier head — plus FP8 on the attention Q/K/V BMMs and softmax. All output quantizers disabled. |
Usage
torch_tensorrt_ptq.py
Script — quantize and (optionally) Torch-TensorRT-compile a ViT.
| Flag | Default | Description |
|---|---|---|
--model_id |
google/vit-large-patch16-224 |
HuggingFace model id of the ViT classifier to quantize. |
--recipe |
huggingface/vit/ptq/fp8 |
Recipe path (relative to modelopt_recipes/ or an absolute YAML). |
--calib_samples |
1024 |
Number of tiny-imagenet samples to use for calibration. |
--batch_size |
128 |
Batch size for calibration / TRT compile. |
--save_dir |
./modelopt_quantized |
Directory the quantized Model Optimizer state-dict (FP16 weights + Q/DQ metadata) is always saved to, as vit_modelopt_state.pt — re-usable across runs without recalibration. |
--skip_trt |
off | Quantize + run the fake-quant model only; skip torch_tensorrt.compile. Useful for environments without Torch-TensorRT installed. |
--layer_info_path |
unset | If set, write the compiled TRT engine's per-layer info (get_layer_info()) to this file. |
# Custom model + custom recipe, saving the quantized state elsewhere.
python torch_tensorrt_ptq.py \
--model_id <huggingface/model-id> \
--recipe <recipe-path-relative-to-modelopt_recipes-or-absolute-yaml> \
--save_dir ./my_quantized
# Dump the compiled engine's per-layer info to inspect FP8 fusion.
python torch_tensorrt_ptq.py --layer_info_path ./vit_fp8_layers.txt
torch_tensorrt_accuracy.py
Script — quantize, compile, and score on ImageNet (see Evaluate Accuracy).
| Flag | Default | Description |
|---|---|---|
--model_id |
google/vit-large-patch16-224 |
HuggingFace model id of the ViT classifier to quantize and score. |
--recipe |
huggingface/vit/ptq/fp8 |
Recipe path (relative to modelopt_recipes/ or an absolute YAML). |
--calib_samples |
1024 |
Number of tiny-imagenet samples to use for calibration. |
--batch_size |
128 |
Calibration / compile / eval batch size. The Torch-TRT engine is dynamic (min=1, opt=max(--batch_size, 2), max=1024) and handles any batch including the trailing partial batch. |
--eval_data_size |
full 50k | Number of ImageNet validation images to score. |
--imagenet_path |
ILSVRC/imagenet-1k |
HF dataset card or local path to the ImageNet validation set (gated). |
--baseline |
off | Also score the unquantized model as a reference. It is Torch-TensorRT-compiled like the quantized model (or run eager under --skip_trt) so the comparison is apples-to-apples. |
--skip_trt |
off | Score the fake-quant (Model Optimizer) model; skip torch_tensorrt.compile. Useful for environments without Torch-TensorRT installed. |
--results_path |
unset | If set, write the accuracy results to this CSV path. |
Evaluate Accuracy
torch_tensorrt_accuracy.py reuses the quantize → compile pipeline above and reports ImageNet-1k top-1 / top-5 accuracy via the onnx_ptq example's evaluate() harness (examples/onnx_ptq/evaluation.py):
python torch_tensorrt_accuracy.py \
--recipe huggingface/vit/ptq/fp8 \
--batch_size 128 \
--baseline \
--eval_data_size 5000 \
--results_path results.csv
--baselinealso scores the unquantized model. It is Torch-TensorRT-compiled the same way as the quantized model, so every reported number comes from the same TRT runtime (pass--skip_trtto score the eager / fake-quant models instead).- The eval uses a dynamic engine (default
--batch_size 128) for both precisions, so it serves the trailing partial batch at any batch size. --results_path results.csvwrites the metrics table (Metric,Top1 (%),Top5 (%)) to CSV.
Note
Validation uses the gated
ILSVRC/imagenet-1ksplit: accept its license / setHF_TOKEN, or point--imagenet_pathat a local copy.evaluate()shuffles the split, so a partial--eval_data_sizedraws a different random subset each run — omit it (full 50k set) for a stable, comparable score.
Custom Recipes
Use --recipe <path> to plug in a different recipe — either a path relative to modelopt_recipes/ (resolved against the built-in recipe library) or an absolute filesystem path to a YAML file. The recipe is loaded via modelopt.recipe.load_recipe, must declare metadata.recipe_type: ptq and a quantize: section, and its quantize config is passed straight to mtq.quantize. See the existing modelopt_recipes/huggingface/vit/ptq/*.yaml for the patterns used here.
Resuming From a Saved Checkpoint
torch_tensorrt_ptq.py always saves the quantized Model Optimizer state to <save_dir>/vit_modelopt_state.pt (default --save_dir ./modelopt_quantized) via mto.save. To reload it without recalibrating, restore it onto a freshly-loaded model before the TRT compile step:
import modelopt.torch.opt as mto
mto.restore(model, "./modelopt_quantized/vit_modelopt_state.pt")
Note
See the save / restore guide for the full
mto.save/mto.restoreworkflow.