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

[PR #5855] [MERGED] Remove no longer supported max vram var #22483

New Issue
Closed
opened 2026-04-19 16:22:25 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-19 16:22:25 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/5855
Author: @dhiltgen
Created: 7/22/2024
Status: ✅ Merged
Merged: 7/22/2024
Merged by: @dhiltgen

Base: main ← Head: remove_max_vram

📝 Commits (1)

  • cc269ba Remove no longer supported max vram var

📊 Changes

3 files changed (+2 additions, -16 deletions)

View changed files

📝 cmd/cmd.go (+0 -1)
📝 envconfig/config.go (+0 -13)
📝 integration/concurrency_test.go (+2 -2)

📄 Description

The OLLAMA_MAX_VRAM env var was a temporary workaround for OOM scenarios. With Concurrency this was no longer wired up, and the simplistic value doesn't map to multi-GPU setups. Users can still set num_gpu to limit memory usage to avoid OOM if we get our predictions wrong.

Fixes #5754

🔄 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/5855 **Author:** [@dhiltgen](https://github.com/dhiltgen) **Created:** 7/22/2024 **Status:** ✅ Merged **Merged:** 7/22/2024 **Merged by:** [@dhiltgen](https://github.com/dhiltgen) **Base:** `main` ← **Head:** `remove_max_vram` --- ### 📝 Commits (1) - [`cc269ba`](https://github.com/ollama/ollama/commit/cc269ba0943ee1fa0bddcce8027d0a6d1b86fec5) Remove no longer supported max vram var ### 📊 Changes **3 files changed** (+2 additions, -16 deletions) <details> <summary>View changed files</summary> 📝 `cmd/cmd.go` (+0 -1) 📝 `envconfig/config.go` (+0 -13) 📝 `integration/concurrency_test.go` (+2 -2) </details> ### 📄 Description The OLLAMA_MAX_VRAM env var was a temporary workaround for OOM scenarios. With Concurrency this was no longer wired up, and the simplistic value doesn't map to multi-GPU setups. Users can still set `num_gpu` to limit memory usage to avoid OOM if we get our predictions wrong. Fixes #5754 --- <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-19 16:22:25 -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#22483
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?