-
Notifications
You must be signed in to change notification settings - Fork 844
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
Unable to run Text to Image and Image to Text models on NPU. [NPU Excluded] #2680
Comments
Can you provide more details, please? Can you confirm whether the used models make use of dynamic shapes? |
in line number 6 we can see that npu is being excluded |
Initially many Jupyter notebooks have NPU excluded when dynamic (input- and/or output-shapes) are involved. For some models it's possible to manually with changes (source code and/or model) get it working for NPU, but not for all. Let's see what the OpenVINO-Notebooks development-team says. |
I’ve observed this issue across several notebooks, except for an RAG-based notebook where the NPU was included for the embedding model. Line no 18 |
Yes, typically this is the case for models using dynamic shapes; but many (the majority?) models are supported and the NPU can perfectly used for e.g. offloading CPU and GPU.
|
Line no 18 In this notebook they mentioned it for embedding model |
When pipelines consist of multiple models, then one or some or the models could "run on the NPU", wile the others run on other devices (CPU, GPU, VPU, FPGA, AUTO, MULTI, HETERO). Let's see of someone from the developer team can comment, maybe it is outdated or a left-over? |
I reviewed the notebooks for both image generation and multimodal tasks, and in all of them, I noticed that the NPU is either not detected or excluded from selection when detected. I want to run these models on the NPU.
Is there an alternative approach I can try, or should I wait for the next update? Could there be something wrong with my current method? Please assist me with this. Thank you.
The text was updated successfully, but these errors were encountered: