mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-11 00:04:08 -05:00
Application slows down for all users after a single user creates excessively large chats. #3519
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#3519
Reference in New Issue
Block a user
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?
Originally created by @ReinderVosDeWael on GitHub (Jan 31, 2025).
Bug Report
Installation Method
We use an Open WebUI docker image hosted as an Azure Container App with an Azure Files volume mount for data persistence.
LiteLLM and a custom proxy server (for models not well supported by LiteLLM) are also used, but likely irrelevant to this report.
Environment
Confirmation:
Expected Behavior:
The application continues functioning at the regular speed
Actual Behavior:
The application slows down to the point of being entirely unusable, with each request to the database taking seconds or timing out entirely.
Description
Bug Summary:
We host an internal OpenWebUI server that allows our employees to use our LLMs. This server is hosted as an Azure Container Application, with a Azure Files volume mount for data persistence.
One of our users likes to upload many files and interact with these. They also prefer to maintain few, long chats rather than many small ones. Once these chats started reaching excessively large sizes (several >20MB, highest 75MB), the application slowed down so much it was effectively unusable for all users. Any interaction with the SQL database would take several seconds or even fail entirely. I, as an admin, was not able to access this user's chats or delete the user account because these requests would time out. I ended up downloading the sqlite database, removing the user's chats from that database, and uploading this modified database back to Azure. This resolved the issue.
Reproduction Details
Steps to Reproduce:
Create a database with several massive chats, and attempt to perform any database query.
Additional Information
I appreciate that this usage of Open WebUI is far beyond the 'intended use-case', and that this can be resolved by instructing users that this behavior causes severe issues. Nevertheless, I'm wondering whether there is something we can do to prevent the application from failing as catastrophically should this happen again.