-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
View output from Comfy in Runpod logs #76
Comments
FWIW, my pipe idea worked -- I can now see the comfy output in the Runpod Serverless logs. You have to add Then, in rp_handler.py,
However, I am still confused as to why the endpoint is running so slowly. It takes 10-20x longer on the NVIDIA A100-SXM4-80GB Runpod server than it does on my local 3080 Ti. |
I realize that I should probably move this out of Issues, but I just realized that the Docker image is based on nvidia/cuda:11.8.0, but then PyTorch is installing from the 12.1 repo. Is this a problem? |
i noticed that too and changed it to:
|
Yeah, the next thing that should happen here is to actually update to CUDA 12.1 as this should improve the performance overall. And yes, seeing the output of ComfyUI would also be nice. |
Is your feature request related to a problem? Please describe.
Background: My endpoint is running super slow on RunPod (NVIDIA A100-SXM4-80GB), and I don't know why. When I run my Docker container locally (3080 Ti), it runs at the expected speed. As a benchmark, comfyui_face_parsing custom node loads in 0.8 seconds locally, but takes 5.9 seconds on RunPod. So I'm trying to figure out what is wrong.
Problem: When I run the Docker image locally, I can see both the output of rp_handler.py AND the output of Comfy. I imagine this would be super helpful in diagnosing the slowness. But when I watch the logs of the Serverless worker on RunPod, I can see the output of rp_handler.py, but none of the output of Comfy.
Describe the solution you'd like
I'd like to be able to see output from Comfy in the Worker logs as workflows are running.
Describe alternatives you've considered
I see two possible solutions:
Additional context
I am not at all confident that I am diagnosing this logging problem correctly. Should I be seeing the comfy output in the RunPod worker logs? Are my possible solutions the only way? Or am I missing something obvious?
The text was updated successfully, but these errors were encountered: