github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-17 05:36:16 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #15598] MLX backend for image generation wastes a lot of CPU time #72015

New Issue
Open
opened 2026-05-05 03:19:25 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-05 03:19:25 -05:00
Owner
Copy Link

Originally created by @yurivict on GitHub (Apr 15, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15598

Here is the threads load pattern:

Image

ollama runs 77 threads of which 32 theads perodically become active in bursts. Only 1 CPU is active for long periods of time between bursts. It looks like only ~30% of CPU is actually used on average.

This program was used to measure the CPU load and to make this plot.

CPU: AMD Ryzen 9 9950X 16-Core Processor
Version: 0.20.7
OS: FreeBSD 15 STABLE

Originally created by @yurivict on GitHub (Apr 15, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15598 Here is the threads load pattern: <img width="2735" height="1166" alt="Image" src="https://github.com/user-attachments/assets/37220429-9738-41e0-a8d2-aaed535dfffe" /> ollama runs 77 threads of which 32 theads perodically become active in bursts. Only 1 CPU is active for long periods of time between bursts. It looks like only ~30% of CPU is actually used on average. [This program](https://freebsd.org/~yuri/monitor-process-active-threads.py) was used to measure the CPU load and to make this plot. CPU: AMD Ryzen 9 9950X 16-Core Processor Version: 0.20.7 OS: FreeBSD 15 STABLE
GiteaMirror commented 2026-05-05 03:19:28 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15598
Analyzed: 2026-04-18T18:19:32.814856

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274305076 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15598 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15598 **Analyzed**: 2026-04-18T18:19:32.814856 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
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
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#72015
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?