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
{{ message }}
This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
In the scenario below, I enabled a CR Multi-ControlNet Stack node with 3 controlnets (Canny, Depth, and OpenPose). The stack conditions a KSampler Advanced Efficient node.
Doing so enormously increases the generation time: all things equal, the SDXL base model goes from ~3min30s / image (I'm on a Mac...) to ~8min50s / image.
If I modify the stack to only use 2 controlnets, the generation time goes down to ~6min36s / image.
With 1 controlnet only, the generation time goes down to ~4min51s / image.
Is this behavior normal? I don't recall ControlNet influencing generation time in A1111 or SD Next, even when I used 3 at a time, like in this case.
(I noticed this a while ago. It's not something new. I just didn't report it before because I wasn't certain it's an anomaly)
The text was updated successfully, but these errors were encountered:
I would try and see how long it takes when you try to reproduce the workflow as closely as possible using auto1111 for reference. If I didn't have a diff issue w/efficiency nodes now, I would try to run your workflow on my hardware for comparison.
Is there a way to reach you? I have tried and there was no response. Trying to see if you could assist on a project. I have no issue sending a tribute or patron donation.
In the scenario below, I enabled a
CR Multi-ControlNet Stack
node with 3 controlnets (Canny, Depth, and OpenPose). The stack conditions aKSampler Advanced Efficient
node.Doing so enormously increases the generation time: all things equal, the SDXL base model goes from ~3min30s / image (I'm on a Mac...) to ~8min50s / image.
If I modify the stack to only use 2 controlnets, the generation time goes down to ~6min36s / image.
With 1 controlnet only, the generation time goes down to ~4min51s / image.
Is this behavior normal? I don't recall ControlNet influencing generation time in A1111 or SD Next, even when I used 3 at a time, like in this case.
(I noticed this a while ago. It's not something new. I just didn't report it before because I wasn't certain it's an anomaly)
The text was updated successfully, but these errors were encountered: