-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
ggml : remove OpenCL #7735
ggml : remove OpenCL #7735
Conversation
ggml-ci
@ggerganov Fyi, Vulkan still suffers substantial memory allocation issue, especially with large context sizes (which are still within the model specifications), reported multiple times. Removing Clblast before this was fixed is a really bad move. It essentially locks users with 16GB RAM out of 7B models in good quantization, and larger models. Judging by this PR, the footprint of Clblast was minimal, so removing it doesn't make sense. As much as I want it, current implementation of Vulkan does not supersede Clblast. Additionally, you didn't even announce this change as you did previously with similar ones. I understand, that technically it's not a breaking change, but it's an important feature, even if it was partly (MoE, mostly) broken for a long time. |
Partially revert "ggml: remove OpenCL (ggerganov#7735)" Restore functionality, skip documentation
This reverts commit 554c247.
With CLBLAST I was able to run small models on my integrated Skylake GT2 [HD Graphics 520] with the full 8GB of RAM of my Laptop as VRAM. Will test Vulkan backend, hope it is no regression.. |
Yeah no way Vulkan is an adequate replacement for OpenCL, with CLBLAS my model loads almost instantly and with Vulkan I am stuck at the loading screen.. |
Also with Vulkan I run out of Memory with models that fully load fine with OpenCL.. Vulkan takes endless time and then runs out of memory:
OpenCL loads fine instantly:
Only upside of the Vulkan backend is maybe that if it finally loads on a model it will use ~90% of my GPU compared of ~80% with OpenCL, but I didn't measure yet if this also results in a speedup or only consumes more resources. |
I tried Vulkan again after ignoring for a few months but the latest build crashes shortly after loading. OpenCL just worked no matter what hardware I through my installation on. I'm not sure how vulkan can supersede OpenCL when I just can't trust it to work on alot of users' hardware. It would be better just to say there is no unified library and tell devs they are on their own for compatibility. |
Something is seriously wrong with the vulkan code, when using the vulkan code I get random output like |
CLBlast was versatile and supporting any OpenCL implementation including nvidia, amd, and cpu (for example via PoCL) via OpenCL ICD loader. So it's a pity the support is removed. |
Seriously, Vulkan isn't replacement of OpenCL. Can we get this code back? |
Manually adjusted. This reverts commit 554c247. This reverts commit 257f8e4. Signed-off-by: David Heidelberg <[email protected]>
Superseded by Vulkan