KSampler slowing down when processing is interrupted

[traugdor]

Your question

screenshot of my console. I was interrupting it because I could tell from the preview that it wasn't going to be the image I wanted and I have a pretty large workflow that would take a long time to finish processing.

It started out pretty fast (for my hardware) and then got slower with each interruption.

I haven't noted this behavior until just recently. I think it has something to do with interrupting the workflow.

Logs

No response

Other

OS: Windows 10 Professional
Hardware: CPU Ryzen 7 3700x, GPU Powercolor Radeon 6600xt

Not sure what else is needed. Happy to provide information to help diagnose this issue.

[zeng121]

I had the same problem

[ltdrdata]

Is there no performance degradation if you let the workflow complete fully without interrupting it?

[traugdor]

Is there no performance degradation if you let the workflow complete fully without interrupting it?

not on my end, no, not consistently. Only when interrupting the workflow and starting it again is it consistently reproduce-able. Could be a caching issue? I'm running pretty close to my max VRAM. I'm hesitant to download the latest of ComfyUI and try again simply because I have made edits to some files to fix issues found in #5427 and #3539 pertaining to AMD cards running under DirectML.

when I let it run to completion, the run times of the workflows seems to be most consistent with only slight variations here and there.

[traugdor]

When letting it run to completion it seems that every other run will be significantly faster than the one before

[ltdrdata]

When letting it run to completion it seems that every other run will be significantly faster than the one before

After interrupting, try performing the next execution after taking a sufficiently long break.

[traugdor]

It seems to be exhibiting this behavior more consistently when I am using multiple monitors.

I think it's literally just a VRAM issue at this point.

[traugdor]

Just updating to say that the issue has gotten worse and now I can barely generate a 512x512 image more than a few times before getting allocation errors. Is a VRAM cache not clearing properly? Stopping the Comfy process in Powershell and restarting it usually fixes it, but I cannot generate more than 2 sometimes 3 images without having to restart.

[traugdor]

I downgraded the code several time to a copy from October and the issue still persists, so I think I have a hardware issue.