Keep Model in VRAM #7
Open
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
Attach the OmniGen pipeline to the node instance as an attribute to avoid unloading the model from VRAM after each generation completes.
|
low Varm unfriendly |
|
High vram friendly. I suggest maybe making it as an option perhaps? |
|
I went ahead and added my changes to an existing PR I created, otherwise the PR would have probably failed #13. Thanks for the inspiration @0X-JonMichaelGalindo |
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.
Attach the OmniGen pipeline to the node instance as an attribute to avoid unloading the model from VRAM after each generation completes.
Is this the right way to do this? It works in my local Comfy test, but I am not sure.