Skip to content
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

SDXL. Speedup on default workflow, no speedup if you use lora. #93

Open
Ph0rk0z opened this issue Jan 21, 2025 · 4 comments
Open

SDXL. Speedup on default workflow, no speedup if you use lora. #93

Ph0rk0z opened this issue Jan 21, 2025 · 4 comments

Comments

@Ph0rk0z
Copy link

Ph0rk0z commented Jan 21, 2025

Added FBC to my normal SDXL workflow. Didn't notice any speedup. Used the demo workflow and there is indeed a 2s difference.

Only thing I'm doing is loading LoRA over the SDXL model. I tried adding the node both pre and post but the times don't change.

I'm on linux with latest stable torch and using xformers attention. Set the value to .2 just like the demo. What am I missing?

@blepping
Copy link
Contributor

Are you using an ancestral or SDE sampler?

@Ph0rk0z
Copy link
Author

Ph0rk0z commented Jan 21, 2025

No, but I found the scheduler is the culprit. I went through his workflow piece by piece and found the main difference is it uses exponential. I use sgm_uniform, generally that's my favorite. Simple is out too. Will have to go through all of them.

@blepping
Copy link
Contributor

#87 might be of interest to you - has some research on how different settings affect quality/speed. (I don't believe there was any testing with different schedules yet though.)

@Ph0rk0z
Copy link
Author

Ph0rk0z commented Jan 21, 2025

That helps for flux but XL will be different. Issue is that all the "good" schedulers don't work with this. Either it messes up faces or it provides no speedup. On some turning down the threshold helped. GITS was the most interesting because it really turbo-ed the generations.

I think I know why on flux I had no help from TeaCache either. Nobody has brought up how schedulers affect this so far. IMO, should be a warning to not confuse people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants