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

[PR #8751] Configurable windows CPU process priority for runnner #75058

New Issue
Open
opened 2026-05-05 07:26:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-05 07:26:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/8751
Author: @Lukasr29
Created: 2/1/2025
Status: 🔄 Open

Base: main ← Head: lukasr29/windows-process-priority

📝 Commits (3)

  • 7ed4061 Extend Config and Windows Runner To Be Able To Set Sub Process Priority
  • 6e9b622 Fix Typos
  • ec6351c Typo fix

📊 Changes

2 files changed (+45 additions, -23 deletions)

View changed files

📝 envconfig/config.go (+24 -22)
📝 llm/llm_windows.go (+21 -1)

📄 Description

This is small change regarding to #6905 and #3511.

I have small box (CPU only, W10) where I run ollama which also runs some other important processes.
With process priority set as above normal other processes are becoming slow or unresponsive for time when ollama generates response.
I've implemented small change where I can put expected sub-process priority as env variable (IDLE/ BELOW_NORMAL / NORMAL / ABOVE_NORMAL), leaving "ABOVE_NORMAL" as default value to match current implementation on main.

For my use case I don't care if ollama will respond in minutes instead of seconds, more important is that ollama won't interfere and slow down other running processes.

Please review deeply and share feedback.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/8751 **Author:** [@Lukasr29](https://github.com/Lukasr29) **Created:** 2/1/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `lukasr29/windows-process-priority` --- ### 📝 Commits (3) - [`7ed4061`](https://github.com/ollama/ollama/commit/7ed4061f68a1145b44213b2486bfa646ad5013f5) Extend Config and Windows Runner To Be Able To Set Sub Process Priority - [`6e9b622`](https://github.com/ollama/ollama/commit/6e9b622b9f3b368ec6f77c57a4d2efece1305f87) Fix Typos - [`ec6351c`](https://github.com/ollama/ollama/commit/ec6351cecc47337e858b8a6d74d908e9f2a0d2f5) Typo fix ### 📊 Changes **2 files changed** (+45 additions, -23 deletions) <details> <summary>View changed files</summary> 📝 `envconfig/config.go` (+24 -22) 📝 `llm/llm_windows.go` (+21 -1) </details> ### 📄 Description This is small change regarding to #6905 and #3511. I have small box (CPU only, W10) where I run ollama which also runs some other important processes. With process priority set as above normal other processes are becoming slow or unresponsive for time when ollama generates response. I've implemented small change where I can put expected sub-process priority as env variable (IDLE/ BELOW_NORMAL / NORMAL / ABOVE_NORMAL), leaving "ABOVE_NORMAL" as default value to match current implementation on main. For my use case I don't care if ollama will respond in minutes instead of seconds, more important is that ollama won't interfere and slow down other running processes. Please review deeply and share feedback. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-05 07:26:37 -05:00
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 pull-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#75058
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?