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
It would be excellent to be able to interrogate the API to determine which models are running at any given time, rather than just seeing which checkpoints were pulled.
I use a variety of clients to interact with Ollama's API. I sometimes run models with a long keep_alive and assume others have similar use cases.
The only way I know of to identify a running model is through processes: ps aux | grep -- '--model' | grep -v grep | grep -Po '(?<=--model\s).*' | cut -d ' ' -f1. This will give you the full path to the model's blob. From there, you can compare that with the output of ollama show --modelfile (or the /api/show endpoint).
I checked the open issues and reddit and didn't see any similar RFIs or requests.
I wrote a bash script (depends on jq) that implements this as POC.
The text was updated successfully, but these errors were encountered:
I think this would be great, along with an ollama ps which shows which models are currently loaded in memory. It should include when the model's TTL is going to expire as well.
It would be excellent to be able to interrogate the API to determine which models are running at any given time, rather than just seeing which checkpoints were pulled.
I use a variety of clients to interact with Ollama's API. I sometimes run models with a long
keep_alive
and assume others have similar use cases.The only way I know of to identify a running model is through processes:
ps aux | grep -- '--model' | grep -v grep | grep -Po '(?<=--model\s).*' | cut -d ' ' -f1
. This will give you the full path to the model's blob. From there, you can compare that with the output of ollama show --modelfile (or the /api/show endpoint).I checked the open issues and reddit and didn't see any similar RFIs or requests.
I wrote a bash script (depends on jq) that implements this as POC.
The text was updated successfully, but these errors were encountered: