Is your feature request related to a problem? Please describe.
We are running openweb at a large-ish internal scale and noticed very slow websocket responses. We were able to track to Redis (single threaded) being able to only do so much throughput. Increasing io-threads on redis helped the problem, but still wasn't great and required us to scale redis vertically and we eventually hit bandwidth limits (red-lining interface).
Describe the solution you'd like
It would be nice if the option for different redis configurations could be supported (IE. Cluster, Sentinel). I was able to work around our issue with a patch file that adds redis cluster support (willing to PR back) and throughput is incredibly fast. The redis-py already supports these configuration as well.
Describe alternatives you've considered
Custom Redis LB solutions (twemproxy) but requires an additional piece of infra that doesn't (afaik) support redis pub/sub. HAProxy does not support out of the box keyspace consitstent hash routing (as it requires parsing TCP and redis proto off the wire).
Originally created by @sleyva-jumptrading on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9863
# Feature Request
**Is your feature request related to a problem? Please describe.**
We are running openweb at a large-ish internal scale and noticed very slow websocket responses. We were able to track to Redis (single threaded) being able to only do so much throughput. Increasing `io-threads` on redis helped the problem, but still wasn't great and required us to scale redis vertically and we eventually hit bandwidth limits (red-lining interface).
**Describe the solution you'd like**
It would be nice if the option for different redis configurations could be supported (IE. Cluster, Sentinel). I was able to work around our issue with a patch file that adds redis cluster support (willing to PR back) and throughput is incredibly fast. The redis-py already supports these configuration as well.
**Describe alternatives you've considered**
- Custom Redis LB solutions (twemproxy) but requires an additional piece of infra that doesn't (afaik) support redis pub/sub. HAProxy does not support out of the box keyspace consitstent hash routing (as it requires parsing TCP and redis proto off the wire).
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 @sleyva-jumptrading on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/9863
Feature Request
Is your feature request related to a problem? Please describe.
We are running openweb at a large-ish internal scale and noticed very slow websocket responses. We were able to track to Redis (single threaded) being able to only do so much throughput. Increasing
io-threadson redis helped the problem, but still wasn't great and required us to scale redis vertically and we eventually hit bandwidth limits (red-lining interface).Describe the solution you'd like
It would be nice if the option for different redis configurations could be supported (IE. Cluster, Sentinel). I was able to work around our issue with a patch file that adds redis cluster support (willing to PR back) and throughput is incredibly fast. The redis-py already supports these configuration as well.
Describe alternatives you've considered