Skip to content

Remove PyTorch multiple instance known issue #80

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 1, 2022
Merged

Remove PyTorch multiple instance known issue #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,14 +218,6 @@ complex execution modes and dynamic shapes. If not specified, all are enabled by
state and a restart of the server may be required to continue serving
successfully.

* Multiple instances of the PyTorch model on GPU do not always
increase performance. Due to thread specific caching in PyTorch, using
multiple instances of the model interact negatively. See
[here](https://github.com/pytorch/pytorch/issues/27902) for more details.
Setting the parameter `DISABLE_OPTIMIZED_EXECUTION` to "true" in the model
configuration may help in some cases to avoid these negative interactions
due to model specific caching and increase multiple instance performance.

* PyTorch does not support Tensor of Strings but it does support models that accept
a List of Strings as input(s) / produces a List of String as output(s). For these models
Triton allows users to pass String input(s)/recieve String output(s) using the String
Expand Down