ComfyUI icon indicating copy to clipboard operation
ComfyUI copied to clipboard

Process stagnant?

Open K-O-N-B opened this issue 1 year ago • 8 comments

Your question

um, after I update Comfyui last week, every time I click queue buttom, client window show "got prompt" image

and, the state bar show this image

I have to wait 30s - 50s every time. After this, the process will start. But this situation not happen last week.

btw, seem only happen in large workflow.

Logs

got prompt
SELECTED: input6
Cee

1girl, solo, long_hair, breasts, looking_at_viewer, skirt, brown_hair, shirt, black_hair, brown_eyes, jewelry, full_body, white_shirt, earrings, parted_lips, shoes, shorts, sleeveless, day, indoors, black_footwear, high_heels, bracelet, from_side, lips, pillow, book, window, kneeling, sleeveless_shirt, bed, chair, black_shorts, sandals, tank_top, curtains, watch, wooden_floor, realistic, wristwatch, computer, hand_on_own_head, bedroom
SELECTED: input6
SELECTED: input1
Warning torch.load doesn't support weights_only on this pytorch version, loading unsafely.
Requested to load SDXL
Loading 1 new model
Warning torch.load doesn't support weights_only on this pytorch version, loading unsafely.
Requested to load SDXL
Loading 1 new model

Other

No response

K-O-N-B avatar Sep 09 '24 18:09 K-O-N-B

What is your ComfyUI version?

ltdrdata avatar Sep 10 '24 01:09 ltdrdata

What is your ComfyUI version?

c27ebeb,

upadte to 967867d today, still same.

K-O-N-B avatar Sep 10 '24 02:09 K-O-N-B

In that case, it seems that at least it's not an issue caused by the old execution model.

Now, the suspicion falls on custom nodes, but since it's described as a large workflow, it's quite a tricky issue because it's difficult to test by removing some custom nodes.

The best approach here seems to be placing logs densely at various suspicious points to narrow down the range causing the problem.

ltdrdata avatar Sep 10 '24 07:09 ltdrdata

In that case, it seems that at least it's not an issue caused by the old execution model.

Now, the suspicion falls on custom nodes, but since it's described as a large workflow, it's quite a tricky issue because it's difficult to test by removing some custom nodes.

The best approach here seems to be placing logs densely at various suspicious points to narrow down the range causing the problem.

Sad, seems like this is a hard problem for newbies to solve

K-O-N-B avatar Sep 10 '24 08:09 K-O-N-B

I have the same problem. So I started with the Default workflow, loaded an SDXL model, everything ran as expected. As soon as I added an IP Adapter, or a Control Net - or even just a Load Image node, that's when it starts getting hung up with "Got Prompt" and yes, a full minute sometimes before it starts doing anything, and this all just started a few days ago after an update.

boundlessliving avatar Sep 10 '24 19:09 boundlessliving

I have the same problem. So I started with the Default workflow, loaded an SDXL model, everything ran as expected. As soon as I added an IP Adapter, or a Control Net - or even just a Load Image node, that's when it starts getting hung up with "Got Prompt" and yes, a full minute sometimes before it starts doing anything, and this all just started a few days ago after an update.

By the way, in the case of IPAdapter, loading insightface is an extremely time-consuming task. It's perfectly normal for it to be slow during the workflow execution, not before the workflow starts.

ltdrdata avatar Sep 11 '24 01:09 ltdrdata

I have the same problem. So I started with the Default workflow, loaded an SDXL model, everything ran as expected. As soon as I added an IP Adapter, or a Control Net - or even just a Load Image node, that's when it starts getting hung up with "Got Prompt" and yes, a full minute sometimes before it starts doing anything, and this all just started a few days ago after an update.

By the way, in the case of IPAdapter, loading insightface is an extremely time-consuming task. It's perfectly normal for it to be slow during the workflow execution, not before the workflow starts.

but the point is this problem not happening before upadte Comfyui 2weeks ago :(

K-O-N-B avatar Sep 11 '24 04:09 K-O-N-B

I have the same problem. So I started with the Default workflow, loaded an SDXL model, everything ran as expected. As soon as I added an IP Adapter, or a Control Net - or even just a Load Image node, that's when it starts getting hung up with "Got Prompt" and yes, a full minute sometimes before it starts doing anything, and this all just started a few days ago after an update.

By the way, in the case of IPAdapter, loading insightface is an extremely time-consuming task. It's perfectly normal for it to be slow during the workflow execution, not before the workflow starts.

but the point is this problem not happening before upadte Comfyui 2weeks ago :(

Can you test which commit the phenomenon starts occurring from?

ltdrdata avatar Sep 11 '24 05:09 ltdrdata

@ltdrdata I also have this issue. It's not isolated to ipadapter or controlnet alone and the workflow doesn't have to be complex. there just seems to be a slight delay before generation.

nux1111 avatar Sep 13 '24 12:09 nux1111

I've update CUI today, seems problem has gone, 2-5 sec can start the process.

K-O-N-B avatar Sep 14 '24 03:09 K-O-N-B

Updating just now did not change anything for me. It's still trying to load all models, seemingly concurrently, whenever I hit Queue. But it seems to be worse with workflows with any "Load Image" nodes - at least for me.

boundlessliving avatar Sep 14 '24 10:09 boundlessliving

LOL

It happen again when I update CUI from cf80d28 to ca08597. I downdate to cf80d28, the speed go normal. @ltdrdata

K-O-N-B avatar Sep 15 '24 01:09 K-O-N-B

I've test again, 2 version of CUI How long does it take from the time you press the queue button to actually start the process: CF80d28:7 secs B3ce8fb: 72 secs

K-O-N-B avatar Sep 15 '24 11:09 K-O-N-B

In my case, solution was to update custom nodes and recreate workflow. There may be some incompatibilities between different nodes and CUI versions I guess.

wisieeen avatar Sep 16 '24 01:09 wisieeen

this problem seems fixed

K-O-N-B avatar Sep 23 '24 02:09 K-O-N-B