github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-12 01:54:38 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

Enhancement: Ollama server prioritisation or selection #1050

New Issue
Closed
opened 2025-11-11 14:36:17 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 14:36:17 -06:00
Owner
Copy Link

Originally created by @nexy7574 on GitHub (May 27, 2024).

Is your feature request related to a problem? Please describe.
Me and a couple friends all run our own instances of Ollama, which are all running on different hardware. For instance, one friend is running Ollama with a GPU, however on a PC, which is not always online. I am running an ollama instance on both my pc, which is CPU-only, however significantly more powerful than my homeserver, which is also running ollama, however with a weak 4-core CPU. In open-webui, adding multiple servers appears to only load-balance, offering no choice of which server runs what, and doesn't allow a failover-style method.

Describe the solution you'd like
A way to define a server priority list. I.e:

  1. Instance 1 with GPU
  2. Instance 2 with powerful CPU - utilised if Instance 1 is unreachable
  3. Instance 3 with weak CPU - always available low-power backup option

Alternatively, being able to select which instance is used in a chat would be equally useful.

Describe alternatives you've considered
Intercepting requests via a reverse proxy, or simply hosting an OWUI instance for each ollama instance (this is suboptimal since we'd then have to create accounts for each instance)

Originally created by @nexy7574 on GitHub (May 27, 2024). **Is your feature request related to a problem? Please describe.** Me and a couple friends all run our own instances of Ollama, which are all running on different hardware. For instance, one friend is running Ollama with a GPU, however on a PC, which is not always online. I am running an ollama instance on both my pc, which is CPU-only, however significantly more powerful than my homeserver, which is also running ollama, however with a weak 4-core CPU. In open-webui, adding multiple servers appears to only load-balance, offering no choice of which server runs what, and doesn't allow a failover-style method. **Describe the solution you'd like** A way to define a server priority list. I.e: 1. Instance 1 with GPU 2. Instance 2 with powerful CPU - utilised if Instance 1 is unreachable 3. Instance 3 with weak CPU - always available low-power backup option Alternatively, being able to select which instance is used in a chat would be equally useful. **Describe alternatives you've considered** Intercepting requests via a reverse proxy, or simply hosting an OWUI instance for each ollama instance (this is suboptimal since we'd then have to create accounts for each instance)
GiteaMirror commented 2025-11-11 14:36:18 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 27, 2024):

Duplicate #1081, #1785, Let's continue our discussion there.

@tjbck commented on GitHub (May 27, 2024): Duplicate #1081, #1785, Let's continue our discussion there.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
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/open-webui#1050
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?