You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From initial tests we noticed that CPU is the blocker and GPU is usually free. So in embedded comfy client, if we can use processpool instead of threadpool and run the same prompt twice, i think we can optimize the GPU even more and get higher FPS
The text was updated successfully, but these errors were encountered:
To test this hypothesis i add a 50ms delay to a basic video passthrough workflow in loadtensor and when i run the prompt once i get 18 FPS and when i run it twice i get 30 FPS. (this is with threadpool)
Now the issue with workflows like dreamshaper etc that the checkpoint loading functions are not threadsafe, so need to figure that out
varshith15
changed the title
Running multiple processes for the same prompt
Running multiple processes/threads for the same prompt
Feb 19, 2025
From initial tests we noticed that CPU is the blocker and GPU is usually free. So in embedded comfy client, if we can use processpool instead of threadpool and run the same prompt twice, i think we can optimize the GPU even more and get higher FPS
The text was updated successfully, but these errors were encountered: