-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[NV RTX EP] Set Compute Capability only on Turing architecture #25446
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
[NV RTX EP] Set Compute Capability only on Turing architecture #25446
Conversation
|
Did we ask TRT-RTX guys why setting "current" profile causes perf regression ? |
Did not get a response yet on the root cause for this. For current state of TRT RTX this was the change suggested. |
|
/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows x64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline |
|
Azure Pipelines successfully started running 5 pipeline(s). |
Yes, change should be in the TRT RTX. But this WAR is fine for now. |
|
ok. the WAR makes sense then. Thanks. |
…soft#25446) ### Description <!-- Describe your changes. --> Set compute capability only on Turing arch ### Motivation and Context <!-- - Why is this change required? What problem does it solve? - If it fixes an open issue, please link to the issue here. --> Setting the native compute capability was causing a regression in performance. @gaugarg-nv @ishwar-raut1 @ankan-ban
…soft#25446) ### Description <!-- Describe your changes. --> Set compute capability only on Turing arch ### Motivation and Context <!-- - Why is this change required? What problem does it solve? - If it fixes an open issue, please link to the issue here. --> Setting the native compute capability was causing a regression in performance. @gaugarg-nv @ishwar-raut1 @ankan-ban
Description
Set compute capability only on Turing arch
Motivation and Context
Setting the native compute capability was causing a regression in performance.
@gaugarg-nv @ishwar-raut1 @ankan-ban