langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-25 13:36:01 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

即使是只包含三个节点，将用户问题原样返回的工作流，在并发测试60个请求时，初始响应时间达到了4秒，完全响应时间达到8秒 #6891

New Issue
Closed
opened 2026-02-21 18:17:50 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:17:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @yg2024 on GitHub (Nov 22, 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

即使是只包含三个节点，将用户问题原样返回的工作流，在并发测试60个请求时，初始响应时间达到了4秒，完全响应时间达到8秒

如果只测试一个请求就很快，在一秒左右，但只要同时请求数量一多，即使配置的工作流再简单，也会变慢很多

dify有进行过压测吗？？？

Even with only three nodes, the workflow that returns user questions as they are achieved an initial response time of 4 seconds and a full response time of 8 seconds when testing 60 concurrent requests

If only one request is tested, it will be fast, in about a second, but as long as there are a large number of requests at the same time, even if the configured workflow is simple, it will be much slower

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @yg2024 on GitHub (Nov 22, 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 即使是只包含三个节点，将用户问题原样返回的工作流，在并发测试60个请求时，初始响应时间达到了4秒，完全响应时间达到8秒 如果只测试一个请求就很快，在一秒左右，但只要同时请求数量一多，即使配置的工作流再简单，也会变慢很多 dify有进行过压测吗？？？ Even with only three nodes, the workflow that returns user questions as they are achieved an initial response time of 4 seconds and a full response time of 8 seconds when testing 60 concurrent requests If only one request is tested, it will be fast, in about a second, but as long as there are a large number of requests at the same time, even if the configured workflow is simple, it will be much slower ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:17:51 -05:00
yindo commented 2026-02-21 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 22, 2024):

Well we do have business plan, if you are interested in it. Please feel free to contact our business@dify.ai.

If you are not satisfied with the performance. Please find a way to contribute to it, this is how open source works.

@crazywoola commented on GitHub (Nov 22, 2024): Well we do have business plan, if you are interested in it. Please feel free to contact our business@dify.ai. If you are not satisfied with the performance. Please find a way to contribute to it, this is how open source works.
yindo commented 2026-02-21 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@yg2024 commented on GitHub (Nov 22, 2024):

SERVER_WORKER_AMOUNT和CELERY_WORKER_AMOUNT 加大后效果好很多，看样子不能直接使用默认值

@yg2024 commented on GitHub (Nov 22, 2024): SERVER_WORKER_AMOUNT和CELERY_WORKER_AMOUNT 加大后效果好很多，看样子不能直接使用默认值
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6891
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?