langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Unable to achieve high concurrency with heavy database load. #21456

New Issue
Closed
opened 2026-02-21 20:12:37 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:12:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @OPSTime on GitHub (Jan 5, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.11.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Stress testing Dify revealed that the PostgreSQL database generated a large number of locks and rollbacks, resulting in Dify API reporting database connection timeout errors.

Image

✔️ Expected Behavior

success

❌ Actual Behavior

fail

Originally created by @OPSTime on GitHub (Jan 5, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.11.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Stress testing Dify revealed that the PostgreSQL database generated a large number of locks and rollbacks, resulting in Dify API reporting database connection timeout errors. <img width="1265" height="405" alt="Image" src="https://github.com/user-attachments/assets/22947eab-6419-42c0-8888-f987f7618666" /> ### ✔️ Expected Behavior success ### ❌ Actual Behavior fail
yindo added the 🐞 bug label 2026-02-21 20:12:37 -05:00
yindo closed this issue 2026-02-21 20:12:38 -05:00
yindo commented 2026-02-21 20:12:38 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 5, 2026):

The Community Edition uses default configurations, optimized for one-click launch. If you have performance requirements, please use our Commercial Edition; you can contact business@dify.ai. Moreover, this is not a bug report.

@crazywoola commented on GitHub (Jan 5, 2026): The Community Edition uses default configurations, optimized for one-click launch. If you have performance requirements, please use our Commercial Edition; you can contact business@dify.ai. Moreover, this is not a bug report.
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 🐞 bug
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#21456
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?