🐛 [Bug] Part of the weights are placed to CPU during compilation
Open
Nobody has claimed this yet.
bug
Story: Runtime & Memory & Serialization
- Dominant language
- Python
- Stars
- 3k
- Forks
- 410
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 78
Description
Bug Description
When compiling Bert, a device mismatch occurs. This seems to be caused by weights moved to CPU during compilation.
To Reproduce
Steps to reproduce the behavior:
Run this script:
import torch
import torch_tensorrt as torchtrt
from transformers import BertModel
inputs = [
torch.randint(0, 2, (1, 14), dtype=torch.int32).to("cuda"),
]
model = BertModel.from_pretrained("bert-base-uncased").eval().to("cuda")
enabled_precisions = {torch.float}
debug = True
min_block_size = 1
use_python_runtime = False
exp_program = torch.export.export(model, tuple(inputs))
trt_gm = torchtrt.dynamo.compile(
exp_program,
tuple(inputs),
use_python_runtime=use_python_runtime,
enabled_precisions=enabled_precisions,
debug=debug,
min_block_size=min_block_size,
immutable_weights=False,
)
Expected behavior
Environment
Build information about Torch-TensorRT can be found by turning on debug messages
- Torch-TensorRT Version (e.g. 1.0.0): main branch
- PyTorch Version (e.g. 1.0): nightly
- OS (e.g., Linux): LInux
- How you installed PyTorch (
conda,pip,libtorch, source): pip
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the provided Bert reproduction script and tracing the torchtrt.dynamo.compile entry point with debug output. Check where model weights change devices during compilation; done means compilation completes without a device mismatch and the compiled model keeps the expected GPU placement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- compilers, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100