Qualcomm: 16a16w quantization is much less accurate than 16a8w
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 55/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- python, pytorch
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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
- 主要言語
- Python
- スター
- 5k
- フォーク
- 1.2k
- 平均マージ
- 2日 12時間
- マージ済み PR(30日)
- 588
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pytorch/executorch のほかの issue
-
enhancement triaged
難易度 2/5 半日 初心者へのやさしさ 68/100
pytorch/executorch#21640 ·
-
enhancement module: cuda module: examples module: mlx module: vulkan module: xnnpack
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
pytorch/executorch#23131 · リアクション 1 件 ·
-
good first issue module: examples module: webgpu
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
pytorch/executorch#23099 ·
-
good first issue module: examples module: vulkan
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
pytorch/executorch#23098 ·
-
good first issue module: cuda module: examples
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
pytorch/executorch#23097 ·
pytorch/executorch の issue をすべて見る
似ている issue
-
agent-ready documentation needs-triage
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
-
documentation
難易度 1/5 1時間未満 初心者へのやさしさ 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" オープン
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
-
instance instance add
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
searxng/searx-instances#939 · コメント 1 件 ·
-
area-deployment area-integrations triage:bot-seen
難易度 2/5 半日 初心者へのやさしさ 86/100