the interface very slow #4409

Closed
opened 2026-02-21 18:06:17 -05:00 by yindo · 2 comments
Owner

Originally created by @cjdxhjj on GitHub (Jul 3, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.11

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

refresh the web ui

✔️ Expected Behavior

No response

Actual Behavior

image

Originally created by @cjdxhjj on GitHub (Jul 3, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.11 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce refresh the web ui ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior ![image](https://github.com/langgenius/dify/assets/5616997/c786d8e2-611c-4b45-ac29-8277b3c4eb66)
yindo added the 🐞 bug label 2026-02-21 18:06:17 -05:00
yindo closed this issue 2026-02-21 18:06:17 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jul 3, 2024):

Typical causes of slow performance in the Dify web UI include:

  1. Rate Limits: If the rate limit for the Embedding model API key is reached, it can cause delays.
  2. Token Limits: Setting a high max_tokens value can increase computation time and resource usage.
  3. Server Overload: The server might be overloaded or there could be an error in the application.
  4. Network Issues: Incorrect Nginx configuration can lead to slow performance.

Recommended troubleshooting steps:

  1. Check Rate Limits: Ensure that the rate limit for the Embedding model API key has not been reached.

  2. Adjust max_tokens: Reduce the max_tokens value to decrease computation time.

  3. Server Health: Verify that the server is not overloaded and there are no application errors.

  4. Nginx Configuration: Ensure that Nginx is forwarding the service to the correct location. Use the following command to check container IP addresses and update the Nginx configuration accordingly:

    docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'
    

    Update the Nginx configuration with the correct IP addresses and restart the Nginx container or reload the configuration.

    # Example output
    /docker-web-1: 172.19.0.5
    /docker-api-1: 172.19.0.7
    
    # Update Nginx configuration
    # Replace http://api:5001 with http://172.19.0.7:5001
    # Replace http://web:3000 with http://172.19.0.5:3000
    

    These IP addresses are exemplary; you must execute the command to obtain your own IP address [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 3, 2024): <!-- Answer --> Typical causes of slow performance in the Dify web UI include: 1. **Rate Limits**: If the rate limit for the Embedding model API key is reached, it can cause delays. 2. **Token Limits**: Setting a high `max_tokens` value can increase computation time and resource usage. 3. **Server Overload**: The server might be overloaded or there could be an error in the application. 4. **Network Issues**: Incorrect Nginx configuration can lead to slow performance. Recommended troubleshooting steps: 1. **Check Rate Limits**: Ensure that the rate limit for the Embedding model API key has not been reached. 2. **Adjust `max_tokens`**: Reduce the `max_tokens` value to decrease computation time. 3. **Server Health**: Verify that the server is not overloaded and there are no application errors. 4. **Nginx Configuration**: Ensure that Nginx is forwarding the service to the correct location. Use the following command to check container IP addresses and update the Nginx configuration accordingly: ```bash docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' ``` Update the Nginx configuration with the correct IP addresses and restart the Nginx container or reload the configuration. ```bash # Example output /docker-web-1: 172.19.0.5 /docker-api-1: 172.19.0.7 # Update Nginx configuration # Replace http://api:5001 with http://172.19.0.7:5001 # Replace http://web:3000 with http://172.19.0.5:3000 ``` These IP addresses are exemplary; you must execute the command to obtain your own IP address <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-orchestrate/llms-use-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Author
Owner

@crazywoola commented on GitHub (Jul 3, 2024):

If you are using yarn dev to start the application, yes, it will be slow, because it's development mode.

@crazywoola commented on GitHub (Jul 3, 2024): If you are using `yarn dev` to start the application, yes, it will be slow, because it's development mode.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#4409