github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #20502] issue: Performance Optimization: How can open-webui support high availability and high concurrency? #19204

New Issue
Closed
opened 2026-04-20 01:32:58 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 01:32:58 -05:00
Owner
Copy Link

Originally created by @gongshaojie12 on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20502

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

0.6.43

Ollama Version (if applicable)

No response

Operating System

Centos 7.9

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Open-webui can support high availability and high concurrency.

Actual Behavior

I am using a single-machine installation of open-webui, installed via pip. The current data size is as follows:

489M    ./cache
54G     ./uploads
31G     ./vector_db
9G       webui.db

Currently, the open-webui system experiences slow access. I want to improve its access speed and make it support high concurrency and high availability. Is there a detailed guide on how to convert a pip-installed open-webui into a high-performance, high-concurrency, high-availability system? This guide must ensure that the existing data is not damaged, as it is production data and cannot be lost or corrupted.

Steps to Reproduce

None

Logs & Screenshots

None

Additional Information

No response

Originally created by @gongshaojie12 on GitHub (Jan 9, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20502 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Pip Install ### Open WebUI Version 0.6.43 ### Ollama Version (if applicable) _No response_ ### Operating System Centos 7.9 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Open-webui can support high availability and high concurrency. ### Actual Behavior I am using a single-machine installation of open-webui, installed via pip. The current data size is as follows: ``` 489M ./cache 54G ./uploads 31G ./vector_db 9G webui.db ``` Currently, the open-webui system experiences slow access. I want to improve its access speed and make it support high concurrency and high availability. Is there a detailed guide on how to convert a pip-installed open-webui into a high-performance, high-concurrency, high-availability system? This guide must ensure that the existing data is not damaged, as it is production data and cannot be lost or corrupted. ### Steps to Reproduce None ### Logs & Screenshots None ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 01:32:58 -05:00
GiteaMirror commented 2026-04-20 01:33:00 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Jan 9, 2026):

🔍 Similar Issues Found

I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:

  1. #20327 issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance
    by galvanoid • Jan 02, 2026 • bug

  2. #19843 issue: Intermittent Performance Degradation
    by gneuli • Dec 09, 2025 • bug

💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3727893406 --> @owui-terminator[bot] commented on GitHub (Jan 9, 2026): 🔍 **Similar Issues Found** I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions: 1. [#20327](https://github.com/open-webui/open-webui/issues/20327) **issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance** *by galvanoid • Jan 02, 2026 • `bug`* 2. [#19843](https://github.com/open-webui/open-webui/issues/19843) **issue: Intermittent Performance Degradation** *by gneuli • Dec 09, 2025 • `bug`* --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
GiteaMirror commented 2026-04-20 01:33:01 -05:00
Author
Owner
Copy Link

@Classic298 commented on GitHub (Jan 9, 2026):

Do not open issues if you want to ask a question!

Open a discussion or ask on discord.

the next docs update will have some HA and concurrency guides and new troubleshooting sections

In the meantime search in the discussions and read specifically the conversation, the last 30 comments (not the PR itself) here #16520

<!-- gh-comment-id:3727910523 --> @Classic298 commented on GitHub (Jan 9, 2026): <ins>**Do not open issues if you want to ask a question!**</ins> Open a discussion or ask on discord. the next docs update will have some HA and concurrency guides and new troubleshooting sections In the meantime search in the discussions and read specifically the conversation, the last 30 comments (not the PR itself) here #16520
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
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#19204
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?