TopK 3840 limitation and future plans for this operator
Open
Nobody has claimed this yet.
triaged
- Dominant language
- C++
- Stars
- 13.4k
- Forks
- 2.4k
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
Are there any plans for removing 3840 limitation from TopK operator?
Some time ago I reached a post written by @zerollzeng
It's known limitation, and we are actively working on remove it.
I wonder if some work on this topic is still ongoing. If so, which TensorRT release it targets?
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 with the linked TensorRT TopK operator documentation and review the two comments in this issue for the stated 3840 limitation. Identify whether current TensorRT sources or release plans address removing it; the issue is complete only when a supported change or a clear target release is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100