Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #2014] [MERGED] Ollama performance mode option #3858

New Issue
Closed
opened 2026-02-22 18:34:38 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:34:38 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/2014
Author: @shatfield4
Created: 7/31/2024
Status: ✅ Merged
Merged: 8/2/2024
Merged by: @timothycarambat

Base: master ← Head: 1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses

📝 Commits (4)

  • cb65056 ollama performance mode option
  • aa477a3 Merge branch 'master' into 1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses
  • 2ebfef0 Change ENV prop
  • c2b6408 Merge branch 'master' into 1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses

📊 Changes

4 files changed (+62 additions, -8 deletions)

View changed files

📝 frontend/src/components/LLMSelection/OllamaLLMOptions/index.jsx (+52 -8)
📝 server/models/systemSettings.js (+1 -0)
📝 server/utils/AiProviders/ollama/index.js (+5 -0)
📝 server/utils/helpers/updateENV.js (+4 -0)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #1991

What is in this change?

  • Adds a Performance Mode option to the Ollama provider
  • This allows the user to select Base or Maximum
  • Base option, we do not set numCtx
  • Maximum option, we set numCtx to this.promptWindowLimit()

Additional Information

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 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/Mintplex-Labs/anything-llm/pull/2014 **Author:** [@shatfield4](https://github.com/shatfield4) **Created:** 7/31/2024 **Status:** ✅ Merged **Merged:** 8/2/2024 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses` --- ### 📝 Commits (4) - [`cb65056`](https://github.com/Mintplex-Labs/anything-llm/commit/cb6505617a56fdb2906039114b9e325836d16996) ollama performance mode option - [`aa477a3`](https://github.com/Mintplex-Labs/anything-llm/commit/aa477a390d4d30bfbfc79f09fc8bc4539e132f2d) Merge branch 'master' into 1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses - [`2ebfef0`](https://github.com/Mintplex-Labs/anything-llm/commit/2ebfef0a2ac98b3fc41aae8ef3b34cff32764ef0) Change ENV prop - [`c2b6408`](https://github.com/Mintplex-Labs/anything-llm/commit/c2b6408ee9960264a9be8fbd6fa9f99310e9993c) Merge branch 'master' into 1991-feat-ollama-n_ctx-for-vram-allocation-and-performance-on-responses ### 📊 Changes **4 files changed** (+62 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/components/LLMSelection/OllamaLLMOptions/index.jsx` (+52 -8) 📝 `server/models/systemSettings.js` (+1 -0) 📝 `server/utils/AiProviders/ollama/index.js` (+5 -0) 📝 `server/utils/helpers/updateENV.js` (+4 -0) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [x] ✨ feat - [ ] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #1991 ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> - Adds a `Performance Mode` option to the Ollama provider - This allows the user to select `Base` or `Maximum` - Base option, we do not set `numCtx` - Maximum option, we set `numCtx` to this.promptWindowLimit() ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:34:38 -05:00
yindo closed this issue 2026-02-22 18:34:38 -05:00
yindo changed title from [PR #2014] Ollama performance mode option to [PR #2014] [MERGED] Ollama performance mode option 2026-06-05 15:15:35 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3858
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?