NVIDIA / NVIDIA/TensorRT

result mismatch between qdq-onnx and tensorrt engine.

Open
#4,708 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Module:Accuracy
Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

Description

i tried to use tensort8.6.1 to convert a onnx model with qdq nodes, however, the output of the converted engine dismatched with that of original onnx.

Environment

TensorRT Version:8.6.1 GA

NVIDIA GPU: Geforce 3060

NVIDIA Driver Version:Driver Version: 535.230.02

CUDA Version: nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0

CUDNN Version: 8.6.0

Operating System: ubuntu20.04

Python Version (if applicable):3.9.23

Tensorflow Version (if applicable):

PyTorch Version (if applicable):

Baremetal or Container (if so, version):

Relevant Files

Steps To Reproduce

  1. trtexec --onnx=quant_base.onnx --saveEngine=quant_base.plan --dumpProfile=true --int8 --fp16 --verbose=true > log.log 2>&1
    quant_base.onnx
  2. python _infer.py
    i use randomly generated input to forward onnx and engine, compare their results by calculating cosine similarity.
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with quant_base.onnx using the provided trtexec command, then run _infer.py to compare the ONNX and TensorRT outputs. Check the verbose build log and cosine-similarity result to identify where the QDQ quantization path diverges; done means the mismatch is explained and a verified correction or minimal reproducer is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.