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

[PR #10770] [CLOSED] llm: exclude input layers from VRAM layer size estimation #39229

New Issue
Closed
opened 2026-04-22 23:53:32 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-22 23:53:32 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/10770
Author: @rick-github
Created: 5/19/2025
Status: ❌ Closed

Base: main ← Head: estimation

📝 Commits (1)

  • 4b063a8 llm: exclude input layers from VRAM estimation

📊 Changes

1 file changed (+13 additions, -1 deletions)

View changed files

📝 llm/memory.go (+13 -1)

📄 Description

Input layers only run on CPU, so don't use them when finding the maximum size of a layer in VRAM.

Doesn't completely ease the increased memory reported in the following, but reduces it somewhat:

Fixes: #10765, #10756, #10752, #10726

🔄 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/10770 **Author:** [@rick-github](https://github.com/rick-github) **Created:** 5/19/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `estimation` --- ### 📝 Commits (1) - [`4b063a8`](https://github.com/ollama/ollama/commit/4b063a85cbfec6fed52f96cd38fdb5643042b8a1) llm: exclude input layers from VRAM estimation ### 📊 Changes **1 file changed** (+13 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `llm/memory.go` (+13 -1) </details> ### 📄 Description Input layers only run on [CPU](https://github.com/ollama/ollama/blob/7edfdd2f5f48a7be035cec23b4acd12f7c112e1c/ml/backend/ggml/ggml.go#L248), so don't use them when finding the maximum size of a layer in VRAM. Doesn't completely ease the increased memory reported in the following, but reduces it somewhat: Fixes: #10765, #10756, #10752, #10726 --- <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-04-22 23:53:32 -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#39229
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?