You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I can see both the CPU and the GPU are recognized from the logs, but I don't realy understand how the offloading is split between them.
The consequence is that when I start the container a VM on truenas gets stopped to free some RAM (the model does work after the VM is stopped and there is enough RAM).
Is there a way to make everything work even on this constrained environment? Also, is there a command similar to ollama ps to view where the model is running and the RAM usage?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am trying to use llama.cpp as a docker container on truenas scale, the host system has an AMD GPU and Vulkan is the only option.
This truenas server is mostly full and has only 1 to 2 GB of free RAM.
My question is: is there a way to run the llama.cpp container so that only the GPU VRAM is used?
I tried with various settings in my docker compose:
and I can see both the CPU and the GPU are recognized from the logs, but I don't realy understand how the offloading is split between them.
The consequence is that when I start the container a VM on truenas gets stopped to free some RAM (the model does work after the VM is stopped and there is enough RAM).
Is there a way to make everything work even on this constrained environment? Also, is there a command similar to
ollama psto view where the model is running and the RAM usage?Beta Was this translation helpful? Give feedback.
All reactions