Skip to content

Force/Set CLIP Device — 'cpu' causes long delays #121

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

Open
PrometheusDante opened this issue Apr 5, 2025 · 1 comment
Open

Force/Set CLIP Device — 'cpu' causes long delays #121

PrometheusDante opened this issue Apr 5, 2025 · 1 comment

Comments

@PrometheusDante
Copy link

Hey there, I found the Force/Set CLIP Device node to be causing extreme slowdown in my workflows, when set to 'cpu'.
In particular this line pops up in the console:
Attempting to release mmap (319)
which does not happen when taking the node out of the process. This happens regardless of using regular DualClipLoader or the GGUF version from your other node pack.

Given how Comfy handles this correctly by default now, i.e. no longer defaulting to 'cuda' when VRAM is sparse, the node is not crucial to my workflow anymore, so this is more of a heads up in case others require it and run into this issue.

@city96
Copy link
Owner

city96 commented Apr 23, 2025

Just in case other people are running into it, this commit attempts to fix the slowdown if the model is already on the CPU:
city96/ComfyUI-GGUF@a355f8b

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