github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-09 23:35:09 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: Performance Disparity: API Response Time Variation Between Admin and User Roles #4601

New Issue
Closed
opened 2025-11-11 15:58:12 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 15:58:12 -06:00
Owner
Copy Link

Originally created by @chalitbkb on GitHub (Mar 28, 2025).

In the production environment, when I log in as an admin, the response from ../api/models takes only about 1 second. However, when logging in with regular user permissions, it takes as long as 8-10 seconds, and sometimes up to 30 seconds. I have repeatedly tested this scenario multiple times, and the results consistently demonstrate the same performance disparity between admin and regular user roles.

This significant delay not only extends the loading time after clicking the login button but also impacts the user experience negatively. After the OI logo disappears, there is no clear indication of system activity, such as a loading icon. As a result, the user interface appears to be frozen on a white or black screen, which can be confusing and frustrating for users, making them uncertain whether the system is processing their request or has encountered an error.

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.0

Ollama Version (if applicable)

No response

Operating System

Windows 11

Browser (if applicable)

Chrome 134.0.6998.118

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 listed steps to reproduce the bug in detail.

Expected Behavior

  • In the production environment, the ../api/models API should have consistent and quick response times for all user roles
  • Response time should be within 1-2 seconds, regardless of whether it's an admin or a regular user

Actual Behavior

  • In production, for admin: API responds in 1 second
  • In production, for regular users: API takes 8-10 seconds, sometimes up to 30 seconds

Steps to Reproduce

  1. In the production environment, log in with an admin account
  2. Observe the response of ../api/models in the browser's network tab
  3. Log out
  4. In the production environment, log in with a regular user account
  5. Observe the response of ../api/models in the browser's network tab
  6. Record and compare response times

Logs & Screenshots

ADMIN:
Image

USER:

Image

Additional Information

No response

Originally created by @chalitbkb on GitHub (Mar 28, 2025). In the production environment, when I log in as an admin, the response from ../api/models takes only about 1 second. However, when logging in with regular user permissions, it takes as long as 8-10 seconds, and sometimes up to 30 seconds. I have repeatedly tested this scenario multiple times, and the results consistently demonstrate the same performance disparity between admin and regular user roles. This significant delay not only extends the loading time after clicking the login button but also impacts the user experience negatively. After the OI logo disappears, there is no clear indication of system activity, such as a loading icon. As a result, the user interface appears to be frozen on a white or black screen, which can be confusing and frustrating for users, making them uncertain whether the system is processing their request or has encountered an error. ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.0 ### Ollama Version (if applicable) _No response_ ### Operating System Windows 11 ### Browser (if applicable) Chrome 134.0.6998.118 ### 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 listed steps to reproduce the bug in detail. ### Expected Behavior - In the production environment, the ../api/models API should have consistent and quick response times for all user roles - Response time should be within 1-2 seconds, regardless of whether it's an admin or a regular user ### Actual Behavior - In production, for admin: API responds in 1 second - In production, for regular users: API takes 8-10 seconds, sometimes up to 30 seconds ### Steps to Reproduce 1. In the production environment, log in with an admin account 2. Observe the response of ../api/models in the browser's network tab 3. Log out 4. In the production environment, log in with a regular user account 5. Observe the response of ../api/models in the browser's network tab 6. Record and compare response times ### Logs & Screenshots ADMIN: ![Image](https://github.com/user-attachments/assets/12e20e85-5033-4e95-a945-e7d9a384aaf8) USER: ![Image](https://github.com/user-attachments/assets/a25a29ed-b9bf-4e55-aba8-8e4b83a7a834) ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 15:58:12 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
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#4601
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?