github-starred/ollama-ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-04-27 16:36:54 -05:00
Code Issues 2.2k Packages Projects Releases 100 Wiki Activity

[PR #11332] [MERGED] ggml: Use assigned layers when reporting loading stats #12249

New Issue
Closed
opened 2025-11-12 16:31:53 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-12 16:31:53 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/11332
Author: @jessegross
Created: 7/8/2025
Status: ✅ Merged
Merged: 7/11/2025
Merged by: @jessegross

Base: main ← Head: jessegross/layers

📝 Commits (1)

  • 44e4083 ggml: Use assigned layers when reporting loading stats

📊 Changes

1 file changed (+11 additions, -9 deletions)

View changed files

📝 ml/backend/ggml/ggml.go (+11 -9)

📄 Description

Reporting params.NumGPULayers can be misleading because it is the requested number of layers, not the actual number that is loaded. While they are often the same, there are cases where they might mismatch, such as if the GPU backend is missing.

🔄 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/11332 **Author:** [@jessegross](https://github.com/jessegross) **Created:** 7/8/2025 **Status:** ✅ Merged **Merged:** 7/11/2025 **Merged by:** [@jessegross](https://github.com/jessegross) **Base:** `main` ← **Head:** `jessegross/layers` --- ### 📝 Commits (1) - [`44e4083`](https://github.com/ollama/ollama/commit/44e40837a8208b72601c066c72a6a43147dd9083) ggml: Use assigned layers when reporting loading stats ### 📊 Changes **1 file changed** (+11 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `ml/backend/ggml/ggml.go` (+11 -9) </details> ### 📄 Description Reporting params.NumGPULayers can be misleading because it is the requested number of layers, not the actual number that is loaded. While they are often the same, there are cases where they might mismatch, such as if the GPU backend is missing. --- <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 2025-11-12 16:31:53 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
client2
cloud
compatibility
context-length
create
docker
documentation
embeddings
engine
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
install
integration
intel
js
linux
macos
memory
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
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-ollama#12249
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?