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

[Issue]: Adding quicksettings breaks openvino and will only use CPU #3423

Open
2 tasks done
Enlightnd opened this issue Sep 13, 2024 · 3 comments
Open
2 tasks done

[Issue]: Adding quicksettings breaks openvino and will only use CPU #3423

Enlightnd opened this issue Sep 13, 2024 · 3 comments
Labels
cannot reproduce Reported issue cannot be easily reproducible

Comments

@Enlightnd
Copy link

Issue Description

If you follow the steps in the wiki/Installation guide and add sd_model_refiner, diffusers_pipeline, and sd_backend to the quicksettings menu, suddenly openvino will always use your CPU instead of your GPU.

Version Platform Description

Issue exists on Master and Dev branch.

Relevant log output

No response

Backend

Diffusers

UI

ModernUI

Branch

Master

Model

StableDiffusion 1.5

Acknowledgements

  • I have read the above and searched for existing issues
  • I confirm that this is classified correctly and its not an extension issue
@vladmandic vladmandic changed the title [Issue]: When following the /wiki/Installation guide and add sd_model_refiner, diffusers_pipeline, and sd_backend to quicksettings, openvino breaks and will only use CPU. [Issue]: Adding quicksettings breaks openvino and will only use CPU Sep 13, 2024
@vladmandic
Copy link
Owner

vladmandic commented Sep 13, 2024

this makes no sense since quicksettings are purely just a ui way of displaying it in one place vs another, it changes absolutely nothing in the server or processing. please provide logs that prove this.
(i'm not closing the issue as anything is possible, but really need something to go on)

@vladmandic vladmandic added question Further information is requested cannot reproduce Reported issue cannot be easily reproducible labels Sep 13, 2024
@Enlightnd
Copy link
Author

When I get the time I'll record what is happening.

Before I posted this, I spent quite some time with Disty on discord trying to figure out why openvino would always only use CPU for me.

Even tried the new openvino and torch versions in the dev branch to see what was going on.

Which eventually spit out the following error when disabling the "Model compile suppress errors"

https://media.discordapp.net/attachments/1130536562422186044/1283959378709450814/image.png?ex=66e6de1a&is=66e58c9a&hm=35ad0900929d47474583efaf1645f6bf2546a983a6d0ad57b892826671cf2e92&=&format=webp&quality=lossless&width=636&height=904

Couldn't figure out what may be the cause other than maybe an artefact error from switching back and forth between openvino and ipex, or other "wrong libraries littered on the system" style issues.

So I loaded a fresh windows image, re-installed SD.Next and at first, everything worked perfectly.

Then I went ahead and re-added those quickmenu items as suggested in the installation notes and instantly, SD.next was back to only using CPU and spitting out that error when disabling "suppress errors".

Removing those items from quickmenu instantly fixed the issue too, returning to correctly using the GPU.

@Enlightnd
Copy link
Author

Ps, this is on Windows 11, A770, 32GB ram and 6 Zen3 cores allotted.

I'll be installing SD.Next with ipex and openvino on WSL/Ubuntu 24 and pure Ubuntu 24 later today and I'll report if the same happens there with this hardware config.

@vladmandic vladmandic removed the question Further information is requested label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cannot reproduce Reported issue cannot be easily reproducible
Projects
None yet
Development

No branches or pull requests

2 participants