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

Some questions about memory usage #8946

New Issue
Closed
opened 2026-02-21 18:28:46 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:28:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @1523826455647 on GitHub (Mar 3, 2025).

Originally assigned to: @Yeuoly on GitHub.

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I deployed the v1.0.0 version of dify using Docker. At first, when opening Docker's dify, the task manager showed that the virtual machine vmmenwsl was occupying about 10g of memory. However, as time goes on, even if I don't do anything to the container, its memory usage will continue to increase, even exceeding 20g. This issue does not occur when the dify version is 0.15.3. I am not sure if the dify problem is still caused by Docker, but the current version does occupy more memory than the previous version.

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @1523826455647 on GitHub (Mar 3, 2025). Originally assigned to: @Yeuoly on GitHub. ### 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 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I deployed the v1.0.0 version of dify using Docker. At first, when opening Docker's dify, the task manager showed that the virtual machine vmmenwsl was occupying about 10g of memory. However, as time goes on, even if I don't do anything to the container, its memory usage will continue to increase, even exceeding 20g. This issue does not occur when the dify version is 0.15.3. I am not sure if the dify problem is still caused by Docker, but the current version does occupy more memory than the previous version. ![Image](https://github.com/user-attachments/assets/689e0c82-f27b-4ffd-b7fd-768d9d227195) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🙋‍♂️ question label 2026-02-21 18:28:46 -05:00
yindo closed this issue 2026-02-21 18:28:46 -05:00
yindo commented 2026-02-21 18:28:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

I found a similar discussion regarding memory usage issues with Dify. In a previous case, users experienced high memory usage with the 'plugin_daemon'. The suggested solution was to re-pull the latest Dify code into a different directory on the host and restart Dify. This resolved the issue for the user, as they observed that the memory did not increase continuously after doing so [1].

You might want to try this approach to see if it resolves your memory usage issue with version 1.0.0.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> I found a similar discussion regarding memory usage issues with Dify. In a previous case, users experienced high memory usage with the 'plugin_daemon'. The suggested solution was to re-pull the latest Dify code into a different directory on the host and restart Dify. This resolved the issue for the user, as they observed that the memory did not increase continuously after doing so <sup>[[1]](https://github.com/langgenius/dify/discussions/14665)</sup>. You might want to try this approach to see if it resolves your memory usage issue with version 1.0.0. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e2fd5d42-342f-47ec-a56a-6d3cd917ca77?feedback_type=other)</sup>
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 🙋‍♂️ question
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#8946
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?