github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #4458] Confirm GPU usage command #2787

New Issue
Closed
opened 2026-04-12 13:06:58 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 13:06:58 -05:00
Owner
Copy Link

Originally created by @puddlejumper90 on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/4458

Would like to have a way to to confirm if a GPU is actually being utilized. Maybe some kind of command or option when running a given model to test/log individual machine performance.

Originally created by @puddlejumper90 on GitHub (May 15, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/4458 Would like to have a way to to confirm if a GPU is actually being utilized. Maybe some kind of command or option when running a given model to test/log individual machine performance.
GiteaMirror added the feature request label 2026-04-12 13:06:58 -05:00
GiteaMirror commented 2026-04-12 13:07:00 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (May 15, 2024):

Hey @puddlejumper90 try ollama ps in the upcoming release. It will tell you how what percentage of the model is on the CPU/GPU/both. The output looks like:

NAME         	ID          	SIZE  	PROCESSOR	UNTIL
mixtral:8x22b	bf88270436ed	82 GB 	100% GPU 	4 minutes from now
llama3:latest	71a106a91016	5.9 GB	100% GPU 	About a minute from now
<!-- gh-comment-id:2113612062 --> @pdevine commented on GitHub (May 15, 2024): Hey @puddlejumper90 try `ollama ps` in the upcoming release. It will tell you how what percentage of the model is on the CPU/GPU/both. The output looks like: ``` NAME ID SIZE PROCESSOR UNTIL mixtral:8x22b bf88270436ed 82 GB 100% GPU 4 minutes from now llama3:latest 71a106a91016 5.9 GB 100% GPU About a minute from now ```
GiteaMirror commented 2026-04-12 13:07:01 -05:00
Author
Owner
Copy Link

@puddlejumper90 commented on GitHub (May 16, 2024):

lifesaver, thank you @pdevine!

<!-- gh-comment-id:2113727779 --> @puddlejumper90 commented on GitHub (May 16, 2024): lifesaver, thank you @pdevine!
GiteaMirror commented 2026-04-12 13:07:01 -05:00
Author
Owner
Copy Link

@pdevine commented on GitHub (May 16, 2024):

@puddlejumper90 lmk how it goes. We just shipped the feature yesterday.

<!-- gh-comment-id:2116193504 --> @pdevine commented on GitHub (May 16, 2024): @puddlejumper90 lmk how it goes. We just shipped the feature yesterday.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#2787
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?