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

The frontend application has high memory and CPU usage. #15553

New Issue
Closed
opened 2026-02-21 19:22:16 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:22:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiejx618 on GitHub (Jul 21, 2025).

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.
Image

Dify version

1.6.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Whether I deploy it on WSL (Ubuntu) in Windows or directly on Windows, the memory and CPU usage is consistently very high.

WSL (Ubuntu): The entire Linux system is allocated 12GB of memory. Eventually, the Dify middleware consumes 4GB of memory, while the frontend web (next-server) takes up over 5GB of memory. As a result, the Linux system runs out of memory, and the machine becomes unresponsive.

After moving the web to the external Windows environment, I found that Windows also experiences high memory usage. The memory usage reaches 6GB, and the CPU usage remains at around 60%.

✔️ Expected Behavior

The frontend application should not consume excessive memory and CPU resources

❌ Actual Behavior

No response

Originally created by @xiejx618 on GitHub (Jul 21, 2025). ### 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. <img width="1261" height="638" alt="Image" src="https://github.com/user-attachments/assets/99460bcc-cc36-4655-8fc0-95abaa8283bf" /> ### Dify version 1.6.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce Whether I deploy it on WSL (Ubuntu) in Windows or directly on Windows, the memory and CPU usage is consistently very high. WSL (Ubuntu): The entire Linux system is allocated 12GB of memory. Eventually, the Dify middleware consumes 4GB of memory, while the frontend web (next-server) takes up over 5GB of memory. As a result, the Linux system runs out of memory, and the machine becomes unresponsive. After moving the web to the external Windows environment, I found that Windows also experiences high memory usage. The memory usage reaches 6GB, and the CPU usage remains at around 60%. ### ✔️ Expected Behavior The frontend application should not consume excessive memory and CPU resources ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 19:22:16 -05:00
yindo commented 2026-02-21 19:22:16 -05:00
Author
Owner
Copy Link
Copy Source

@baonudesifeizhai commented on GitHub (Jul 21, 2025):

same problem , i just pnpm build and start for many times and add memory limit . not dify problems

@baonudesifeizhai commented on GitHub (Jul 21, 2025): same problem , i just pnpm build and start for many times and add memory limit . not dify problems
yindo commented 2026-02-21 19:22:16 -05:00
Author
Owner
Copy Link
Copy Source

@HyaCiovo commented on GitHub (Jul 21, 2025):

I think we should replace nextjs with vite or others

@HyaCiovo commented on GitHub (Jul 21, 2025): I think we should replace nextjs with vite or others
yindo commented 2026-02-21 19:22:16 -05:00
Author
Owner
Copy Link
Copy Source

@xiejx618 commented on GitHub (Jul 24, 2025):

Unbelievable! Close it without even having a plan. It is a serious user experience issue

@xiejx618 commented on GitHub (Jul 24, 2025): Unbelievable! Close it without even having a plan. It is a serious user experience issue
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#15553
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?