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

Update operators keep tensors on GPU between ops (where possible) #17

Open
5 tasks
karlhigley opened this issue Mar 2, 2022 · 1 comment
Open
5 tasks
Labels
enhancement New feature or request

Comments

@karlhigley
Copy link
Contributor

  • Create a numpy/cupy dispatch mechanism (like pandas/cudf in NVT)
  • Apply DLpack to pass GPU tensors from Python back-end to other models
  • Update FilterCandidates
  • Update SoftmaxSampling
  • Update Faiss and Feast ops to convert to GPU?
@karlhigley karlhigley added this to the 22.04 milestone Mar 2, 2022
@karlhigley karlhigley added the enhancement New feature or request label Mar 2, 2022
@karlhigley
Copy link
Contributor Author

Depending on how this turns out, we may or may not find it worthwhile to add a graph optimizer to condense multiple operators into a single TritonPythonModel. It would still help us avoid the scheduling overhead associated with passing requests between models, but it might not be a big boost if it combining operators no longer helps us avoid GPU-CPU roundtrip conversions.

@karlhigley karlhigley modified the milestones: 22.04, Future Mar 11, 2022
@karlhigley karlhigley changed the title Update operators to use CuPy where possible and keep tensors on GPU between ops Update operators keep tensors on GPU between ops (where possible) Mar 14, 2022
@karlhigley karlhigley removed this from the Future milestone Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant