CUDA INT8 fake quantization converts channels-last inputs to default contiguous layout
Los mantenedores suelen responder en 2 días
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 50/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Área
- machine-learning
Línea de trabajo
Start with the CUDA fake-quant entry points that call inputs.contiguous() without a memory format, for both per-tensor and per-channel paths, and with the in-place check that rejects channels-last inputs. Run the reproducer in the issue to confirm the output stride changes from (105, 1, 21, 3). Done means the layout is preserved for contiguous_format, channels_last and channels_last_3d, while quantized values stay identical and the CUDA extension tests pass.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
CUDA INT8 fake quantization converts channels-last inputs to the default contiguous memory format. The output has the correct quantized values, but loses the input memory layout.
The main motivation is downstream numerical alignment. In practical use, we observed a substantial downstream numerical mismatch despite identical fake-quant values; preserving the output memory format restored alignment with the layout-preserving reference in that case. The conversion also adds an unnecessary full-tensor copy. The per-tensor and per-channel CUDA entry points both call inputs.contiguous() without a memory format.
Steps/Code to reproduce bug
Run on an unmodified checkout of NVIDIA/Model-Optimizer at 472ecb39ad498a6b0d818583d5b1dc483a708abf with CUDA and the ModelOpt CUDA extension available:
import torch
from modelopt.torch.quantization.extensions import get_cuda_ext
ext = get_cuda_ext(raise_if_failed=True)
x = torch.linspace(-1, 1, 210, device="cuda").reshape(2, 3, 5, 7)
x = x.contiguous(memory_format=torch.channels_last)
amax = torch.tensor(1.0, device="cuda")
y = ext.fake_tensor_quant(x, amax)
reference = ext.fake_tensor_quant(x.contiguous(), amax)
print("input stride:", x.stride())
print("output stride:", y.stride())
print("same quantized values:", torch.equal(y, reference))
print("channels-last output:", y.is_contiguous(memory_format=torch.channels_last))
Observed on the original CUDA implementation:
input stride: (105, 1, 21, 3)
output stride: (105, 35, 7, 1)
same quantized values: True
channels-last output: False
This synthetic reproducer demonstrates the layout side effect. The downstream numerical mismatch described above is an application observation, rather than a result measured by this minimal reproducer.
The public tensor_quant.fake_tensor_quant API reaches the same CUDA implementation. Per-channel quantization through fake_tensor_quant_with_axis and 5D channels_last_3d inputs also lose their memory format. The in-place per-tensor entry point rejects channels-last inputs despite their dense contiguous storage.
Expected behavior
Preserve supported contiguous input memory formats (contiguous_format, channels_last, channels_last_3d) without changing the quantization formula, ranges, or output values. Continue to handle non-contiguous inputs safely.
A possible localized fix is to prepare out-of-place inputs with inputs.contiguous(inputs.suggest_memory_format()) and accept the same contiguous formats in the in-place check. The per-channel kernel already uses the actual axis stride to select its amax. A candidate fix and synthetic regression tests have been prepared.
Verification
The reproducer above was executed against both original and fixed CUDA extensions with PyTorch 2.12.1 / CUDA 13.0. The candidate preserves (105, 1, 21, 3) while retaining identical quantized values.
Synthetic regression tests cover per-tensor, every per-channel axis, in-place behavior, non-contiguous inputs, and FP32/FP16/BF16. The original extension fails 12 channels-last cases; all 76 CUDA extension tests and 47 CPU tensor-quantization tests pass with the candidate.
Who can help?
Quantization maintainers.
System information
- OS: Ubuntu 22.04.5 LTS (container).
- CPU architecture: x86_64.
- GPU: one NVIDIA GeForce RTX 5090, approximately 32 GB.
- Python: 3.12.3.
- ModelOpt: upstream commit
472ecb39ad498a6b0d818583d5b1dc483a708abf. - CUDA toolkit: 13.0 (V13.0.88); driver: 595.71.05.
- PyTorch:
2.12.1+cu130(within the declared PyTorch >=2.10 range). - Also reproduced with PyTorch
2.7.0+cu128/ CUDA 12.8 as supplemental older-version evidence. - Transformers, TensorRT-LLM, ONNXRuntime, TensorRT: not required by the reproducer.
- Lenguaje dominante
- Python
- Estrellas
- 5.5k
- Forks
- 800
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 278
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NVIDIA/Model-Optimizer
-
[Bug] modelopt-mcp: all launcher subprocesses hang when the server runs as a stdio MCP server — missing stdin=DEVNULLPosiblemente ocupada @ChenhanYu la tomó hace 33 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
NVIDIA/Model-Optimizer#2551 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 2 días
-
Puzzletron Progress 6/8 (calculating one block scores) takes 10 to 20 times more than in tutorialQuizá libre de nuevo @tejasng053 la tomó hace 40 días y no hay ningún pull request abierto. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
NVIDIA/Model-Optimizer#1667 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
NVIDIA/Model-Optimizer#3178 ·
Los mantenedores suelen responder en 2 días
-
INT4 packing extension never loads from a read-only installPosiblemente ocupada @ajrasane la tomó hace 6 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
NVIDIA/Model-Optimizer#3025 · 1 asignado ·
Los mantenedores suelen responder en 2 días
-
[Puzzletron] Runtime stats benchmark model computes head size as hidden_size // num_attention_heads instead of reading head_dimPosiblemente ocupada @grzegorz-k-karch la tomó hace 10 días. Abiertobug
NVIDIA/Model-Optimizer#3016 · 1 asignado ·
Los mantenedores suelen responder en 2 días
Todos los issues de NVIDIA/Model-Optimizer
Issues similares
-
curriculum documentation quality
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
githubnext/gh-aw-workshop#5367 ·
Los mantenedores suelen responder en 3 días
-
Create Noise Latents ignores randomize_seed and produces the same noise every runPosiblemente ocupada @griptapeops la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
griptape-ai/griptape-nodes-library-diffusers#127 ·
Los mantenedores suelen responder en 1 día
-
Jenkins capacity report: metrics history is lost when archiving a month failsPosiblemente ocupada @RaphaelFakhri la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
adoptium/infrastructure#4568 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
huggingface/deep-rl-class#723 ·
-
premises-missing
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
WingedGuardian/GENesis-AGI#3928 ·
Los mantenedores suelen responder en 1 día