Qualcomm: 16a16w quantization is much less accurate than 16a8w
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- python, pytorch
- Área
- backend, machine-learning
Línea de trabajo
Start by running the provided host-only reproduction and trace make_quantizer through get_16a16w_qnn_ptq_config. Compare the int16 per-tensor and per-channel weight specifications, including PerChannelParamObserver, to isolate the quantization-parameter discrepancy. Done means 16a16w no longer produces catastrophic SQNR or task-accuracy loss relative to 16a8w.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
QuantDtype.use_16a16w is far less accurate than use_16a8w on the same model. More weight bits should never mean a worse result.
resnet18, host PTQ only (prepare_pt2e / convert_pt2e, no lowering, no device), SQNR of the quantized output against fp32:
| recipe | SQNR vs fp32 |
|---|---|
use_16a8w |
24.49 dB |
use_16a16w |
-1.53 dB |
Same pattern on every model tried: deeplabv3_mobilenet_v3_large 8.14 -> 1.47 dB, mobilenet_v3_large 2.72 -> -0.75 dB. On a real task it is catastrophic: DeepLabV3-MobileNetV3 on VOC2012 scores 63.89% mIoU at 16a8w and 3.38% at 16a16w (fp32 67.52%, 100 calibration images).
Repro:
import torch
import torchvision.models as tvm
from executorch.backends.qualcomm.export_utils import make_quantizer
from executorch.backends.qualcomm.quantizer.quantizer import QuantDtype
from torchao.quantization.pt2e.quantize_pt2e import convert_pt2e, prepare_pt2e
torch.manual_seed(0)
model = tvm.resnet18(weights=tvm.ResNet18_Weights.DEFAULT).eval()
sample = (torch.randn(1, 3, 224, 224),)
probe = torch.randn(1, 3, 224, 224)
with torch.no_grad():
ref = model(probe)
for dtype in (QuantDtype.use_16a8w, QuantDtype.use_16a16w):
quantizer = make_quantizer(quant_dtype=dtype, soc_model="SM8850")
prepared = prepare_pt2e(
torch.export.export(model, sample, strict=False).module(), quantizer)
with torch.no_grad():
for _ in range(16):
prepared(torch.randn(1, 3, 224, 224))
got = convert_pt2e(prepared)(probe)
sqnr = 10 * torch.log10((ref**2).mean() / ((ref - got) ** 2).mean()).item()
print(f"{dtype.name:16s} SQNR vs fp32: {sqnr:7.2f} dB")
Ruled out:
- Not the int32 bias. Counting folded bias elements sitting at the int32 limits gives 0 saturated in both arms (DeepLabV3, 100 calibration images, 520px).
quantize_per_tensorpast int32 saturates rather than wraps, so this is not silent corruption there either. Worth noting separately that the derived bias scale leaves little headroom at 16-bit weights:max|bias/scale|reached 0.999 of int32 in one configuration. - Not the weights. Dequantized weights match between the two arms at 36-48 dB, i.e. the 16-bit weights are essentially exact.
- Not execution. This is fake-quant in PyTorch with convolutions in float, so no HTP and no integer accumulator are involved; the loss comes from the quantization parameters alone.
- Not an unsupported SoC.
validate_16a16w_supportrequires HTP >= V73 and SM8850 is v81.
The activation specs are identical between the two recipes, so the difference is on the weight side: get_16a16w_qnn_ptq_config uses an int16 per-tensor symmetric weight spec (quant_min=-32767, quant_max=32767), and the per-channel path uses weight_dtype=torch.int16 with PerChannelParamObserver. I have not isolated which of those is at fault.
Environment: executorch at 8081eb88, torch 2.14.0+cpu, torchao 0.18.0.dev20260729, torchvision 0.29.0+cpu, QAIRT 2.37.0.250724, Linux x86_64. No device needed.
cc @kimishpatel @jerryzh168 @metascroy @cbilgin @psiddh
- Lenguaje dominante
- Python
- Estrellas
- 5k
- Forks
- 1.2k
- Merge medio
- 2 d 12 h
- PR fusionados (30 d)
- 588
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 pytorch/executorch
-
enhancement triaged
Dificultad 2/5 Medio día Aptitud para principiantes 68/100
pytorch/executorch#21640 ·
-
enhancement module: cuda module: examples module: mlx module: vulkan module: xnnpack
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
pytorch/executorch#23131 · 1 reacción ·
-
good first issue module: examples module: webgpu
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
pytorch/executorch#23099 ·
-
good first issue module: examples module: vulkan
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
pytorch/executorch#23098 ·
-
good first issue module: cuda module: examples
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
pytorch/executorch#23097 ·
Todos los issues de pytorch/executorch
Issues similares
-
agent-ready documentation needs-triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
-
Add https://search.jeremyh.xyz/ Abiertoinstance instance add
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
searxng/searx-instances#939 · 1 comentario ·
-
area-deployment area-integrations triage:bot-seen
Dificultad 2/5 Medio día Aptitud para principiantes 86/100