I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
0.6.33
Ollama Version (if applicable)
No response
Operating System
AWS ECS
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
Redis bandwidth usage is reasonable and/or commensurate with functional gain; configuration of events emitted
Actual Behavior
We have 300+ users and peak around 150-175 active users across multiple regions. We're using Upstash as our redis provider and crossed 200GB bandwidth this month.
OpenWebUI generates a lot of traffic and a lot of this seems superfluous, at least at face value.
Our deployment is on ECS but in single task configuration.
I'm interested in whether this is percieved as an "issue" at medium-high user bases, a configuration issue on our end, or just a debate about whether events should be partly configurable (if not already and I've missed something?).
Thanks!
Steps to Reproduce
Activity associated with normal usage of 300+ users
Logs & Screenshots
n/a
Additional Information
No response
Originally created by @jsweetzer-ea on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18345
### 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 am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
0.6.33
### Ollama Version (if applicable)
_No response_
### Operating System
AWS ECS
### 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
Redis bandwidth usage is reasonable and/or commensurate with functional gain; configuration of events emitted
### Actual Behavior
We have 300+ users and peak around 150-175 active users across multiple regions. We're using Upstash as our redis provider and crossed 200GB bandwidth this month.
OpenWebUI generates a lot of traffic and a lot of this seems superfluous, at least at face value.
Our deployment is on ECS but in single task configuration.
I'm interested in whether this is percieved as an "issue" at medium-high user bases, a configuration issue on our end, or just a debate about whether events should be partly configurable (if not already and I've missed something?).
Thanks!
### Steps to Reproduce
Activity associated with normal usage of 300+ users
### Logs & Screenshots
n/a
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-05 20:46:02 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jsweetzer-ea on GitHub (Oct 15, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18345
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.33
Ollama Version (if applicable)
No response
Operating System
AWS ECS
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Redis bandwidth usage is reasonable and/or commensurate with functional gain; configuration of events emitted
Actual Behavior
We have 300+ users and peak around 150-175 active users across multiple regions. We're using Upstash as our redis provider and crossed 200GB bandwidth this month.
OpenWebUI generates a lot of traffic and a lot of this seems superfluous, at least at face value.
Our deployment is on ECS but in single task configuration.
I'm interested in whether this is percieved as an "issue" at medium-high user bases, a configuration issue on our end, or just a debate about whether events should be partly configurable (if not already and I've missed something?).
Thanks!
Steps to Reproduce
Activity associated with normal usage of 300+ users
Logs & Screenshots
n/a
Additional Information
No response