pytorch / pytorch/TensorRT

🐛 [Bug] Input bindings change b/w fast and global partitioner

Open
#2,260 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug story: Dynamo Frontend & Partitioning
Dominant language
Python
Stars
3k
Forks
410
Avg merge
3d 18h
Merged PRs (30d)
78

Description

Bug Description

Global partitioner:

Torch-TensorRT TensorRT Engine:
  Name: fused_0_engine
  Inputs: [
    id: 0
      name: arg0
      shape: [1, 3, 224, 224]
      dtype: Float
    id: 1
      name: _param_constant0
      shape: [16, 3, 3, 3]
      dtype: Float
    id: 2
      name: _param_constant1
      shape: [16]
      dtype: Float
  ]

Fast partitioner:

Torch-TensorRT TensorRT Engine:
  Name: fused_0_engine
  Inputs: [
    id: 0
      name: arg0
      shape: [1, 3, 224, 224]
      dtype: Float
  ]

To Reproduce

Steps to reproduce the behavior:

Expected behavior

Environment

Build information about Torch-TensorRT can be found by turning on debug messages

  • Torch-TensorRT Version (e.g. 1.0.0):
  • PyTorch Version (e.g. 1.0):
  • CPU Architecture:
  • OS (e.g., Linux):
  • How you installed PyTorch (conda, pip, libtorch, source):
  • Build command you used (if compiling from source):
  • Are you using local sources or building from archives:
  • Python version:
  • CUDA version:
  • GPU models and configuration:
  • Any other relevant information:

Additional context

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 comparing the fast and global partitioner paths that produce the shown TensorRT engine input listings. Reproduce the differing bindings with a minimal case and verify that both partitioners preserve the expected inputs; the issue provides no named files or tests to begin from.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.