-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue to build deberta-v3-base
due to missing validUnaryType &&
datatype on TensorRT 8.6
#3587
Comments
Looks like a known limitation, could you please try latest TRT 9.2? Thanks! |
Can you link me to on how do I get access to latest TRT 9.2 , please? I dont see nightly wheels. |
I tested it with I want to support dynamic batch and sequence sizes, I am running into below warnings which based on my understanding will mean that we will fail there. Can you suggest how to get that working ?
|
it's a warning from transformers(pytorch), I think it means use dynamic shape may caused unexpected behavior when export onnx(e.g. some tensor still become constant) during export onnx. You can ask for help in the transformer repo. |
Closing since no activity for more than 3 weeks, thanks all! |
is there any release or tag of TensorRT 8.6.1 that resolves this issue ? Because I could built it with TRT 9.2.0, but I want to deploy this model on nvidia triton inference server. However, triton tensorRT backend does not yet support newer version of tensorRT than 8.6.1, and the tensorRT runtime version should be the same than the one used to build the engine. What would be my best solution for this problem ? |
Description
I am running into conversion issue while trying to convert
deberta-v3-base
into a TensorRT engine. We run intoMore Trace is present next to MRE.
Environment
TensorRT Version:
8.6
NVIDIA GPU:
V100
NVIDIA Driver Version:
525.105.17
CUDA Version:
12.0
CUDNN Version:
Operating System:
Python Version (if applicable): 3.10
Steps To Reproduce
Also tried following #3124 but to no avail.
The text was updated successfully, but these errors were encountered: