-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
[FEAT] Make cuda available #4
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
environment:
- NVIDIA_VISIBLE_DEVICES=all
runtime: nvidia # https://docs.linuxserver.io/images/docker-plex/#nvidia Append |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
Yes. Should be the correct place. |
You can find the documentation here
|
yes you can do that in the console, but it needs to survive updates etc. I found this due to the same issue. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
The proposed solution involves installing the onnxruntime-gpu package and passing the --cuda argument to Piper’s start script. |
Is this a new feature request?
Wanted change
I would like to have the ability to activate cuda as it is supported by piper itself.
The piper documentation says we need to install
onnxruntime-gpu
and add--cuda
on the start script.Reason for change
Piper should work much faster with cuda support on nvidia cards.
Proposed code change
onnxruntime-gpu
in docker container.EXTRA_PARAMS
With such a variable the user could add additional parameters to the piper start script as they like.
The text was updated successfully, but these errors were encountered: