when running OpenwebUI on k8s, with major amount of users (and instances) the websocket is going crazy with or without redis, and make a lot of request since every client sends usage update on the socket every second so if you have 10k online user, you are going wild.
I recommend to add that as an optional feature that you can control in the settings
Originally created by @itaybar on GitHub (Dec 5, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7629
# Feature Request
when running OpenwebUI on k8s, with major amount of users (and instances) the websocket is going crazy with or without redis, and make **a lot** of request since every client sends usage update on the socket every second so if you have 10k online user, you are going wild.
I recommend to add that as an optional feature that you can control in the settings
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 @itaybar on GitHub (Dec 5, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7629
Feature Request
when running OpenwebUI on k8s, with major amount of users (and instances) the websocket is going crazy with or without redis, and make a lot of request since every client sends usage update on the socket every second so if you have 10k online user, you are going wild.
I recommend to add that as an optional feature that you can control in the settings