feat: add ability to allocate multiple GPUs to runner container #189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… (e.g. 0|1|2,3 - GPUs 0,1,2 would be allocated to first aiModels.json runner)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit allows adding multiple GPUs to a runner container. The
-nvidiaflag in go-livepeer startup can specify multiple gpus by adding a|between the gpu IDs.-nvidia 0|1|2,2will allocate GPUs 0,1 and 2 to first block in aiModels.json. GPU 2 will be allocated to second block in aiModels.json.An extra note, you can control what GPUs are allocated to aiModels.json blocks by the order of the GPUs in the nvidia flag.
-nvidia 1,0will allocate GPU 1 to first aiModels.json block and GPU 0 to second aiModels.json block.