Open
Conversation
Collaborator
|
Hi Diego, thank you for suggesting the change! Could you add some documentation to the inference docs to explain the updated usage of the parameter? |
Author
|
Sounds good, adding this now to |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently Boltz does not provide a way to specify which device to run on when multiple GPUs are available. This backward-compatible pull request addresses that by allowing the user to pass either an int, which is currently the default and communicates how many devices to run, or a comma-separated list, which specifies which devices to run on. A single device can be specified by passing
--devices 1,.