-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
[Feature] Add a pause button #6164
Comments
The implementation of a true pause system would face several significant technical challenges:
|
Interesting. This will allow some kind pause, |
There is a save-load queues custom node (can't remember the name atm), it gives error when installed but works great, say you added a bunch of work on the queue but want to stop and want to continue where you left of (from the very start of current running workflow) you save the queue. close comfy after you open it again when you "load" the queue you saved it immediately starts doing it one by one. Not perfect but really helps when you keep adding stuff and have to log off etc. something like it officially would be great. And for "Pausing" on windows when you select anything on the cmdline window this pauses everything comfy is doing, press space again and it continues the work. This is good when you want to use your gpu for a quick task outside comfy. Of course there are times this cannot go back to work correctly and gives error. Most of the time works ok I guess. |
Feature Idea
Problem: when I launch 10 tasks on ComfyUI, I only have a choice to let them run or stop them
If I want to keep the 10 task in the background without them running, I need to shut down everything.
I still need to keep the remaining tasks without losing them, but yet I still need to pause comfy and potentially liberating a portion of the GPU.
The idea is to have a true pause that let you keep the state of comfy with its remaning taks, but delay their execution until you unpause. In the meantime the pause can alllow you to liberate the memory gpu etc.
That or (#6163) as alternative.
Existing Solutions
No response
Other
No response
The text was updated successfully, but these errors were encountered: