Skip to content
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

Understanding the TopK Limitation #4390

Open
Jumaron opened this issue Mar 19, 2025 · 2 comments
Open

Understanding the TopK Limitation #4390

Jumaron opened this issue Mar 19, 2025 · 2 comments

Comments

@Jumaron
Copy link

Jumaron commented Mar 19, 2025

Hey everyone,

From what I understand, the TopK limitation of 3840 seems to stem from the NMSPlugin, specifically the checkParams function throwing an error. However, it also looks like there's something else going on at runtime that's causing the values to get capped at 3840.

Is there any way to bypass this limitation?

Would resolving this issue necessitate a significant rewrite of the underlying architecture?

Best Regards!

@lix19937
Copy link

If you donot want to rewrite code, you can split the Input then call the topK several times.

@Jumaron
Copy link
Author

Jumaron commented Mar 21, 2025

I made a go around regarding this, but i jsut wonder if the best course for TensorRT would be not to exactly do this or something similiar, splitting the Input in multiple TopK notes? 😶

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants