-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Bug: RPC server doesn't load GPU if I use Vulkan #8536
Comments
The Vulkan backend is using the |
is any plan to support vulkan when using RPC backend? |
I will try to find out how to avoid using |
The extras in the Vulkan backend are not really necessary, all the data that they contain is already present (directly or indirectly) in other fields of the tensor. At this point I think they are only there for legacy reasons, but could be removed with a refactor. |
This patch allows using the Vulkan backend with the RPC backend as tensor->extra is no longer used. Ref: ggerganov#8536
Big thanks 👍
Le jeu. 3 oct. 2024, 12:01, Radoslav Gerganov ***@***.***> a
écrit :
… Closed #8536 <#8536> as
completed via 841713e
<841713e>
.
—
Reply to this email directly, view it on GitHub
<#8536 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYN4BA5Z3SEW2IYQU5IDDZZUIWVAVCNFSM6AAAAABLAGD476VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGUYDCOBWGEZDKMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
* vulkan : do not use tensor->extra This patch allows using the Vulkan backend with the RPC backend as tensor->extra is no longer used. Ref: ggerganov#8536 * Adapt GGML_VULKAN_CHECK_RESULTS to extra removal (Mobile-Artificial-Intelligence#2) --------- Co-authored-by: 0cc4m <picard12@live.de>
What happened?
I compiled llamacpp with Vulkan backend. The "rpc-server" binary is linked to libvulkan but it never uses my GPUs. While "llama-cli" is OK.
Name and Version
version: 3384 (4e24cff)
built with cc (GCC) 14.1.1 20240701 (Red Hat 14.1.1-7) for x86_64-redhat-linux
What operating system are you seeing the problem on?
Linux
Relevant log output
The text was updated successfully, but these errors were encountered: