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

After updating to version 1.10.0, the page becomes very laggy when there are more workflow nodes. #20514

New Issue
Closed
opened 2026-02-21 20:07:47 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:07:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @LiAI-tech on GitHub (Nov 24, 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.

Dify version

1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The version is upgraded from 1.9.1 to 1.10.0, operating a workflow with around 100 nodes.

✔️ Expected Behavior

Drag and drop to view nodes smoothly and fluently

❌ Actual Behavior

Node dragging shows obvious lag and delay

Originally created by @LiAI-tech on GitHub (Nov 24, 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. ### Dify version 1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The version is upgraded from 1.9.1 to 1.10.0, operating a workflow with around 100 nodes. ### ✔️ Expected Behavior Drag and drop to view nodes smoothly and fluently ### ❌ Actual Behavior Node dragging shows obvious lag and delay
yindo added the 🐞 bug label 2026-02-21 20:07:47 -05:00
yindo closed this issue 2026-02-21 20:07:47 -05:00
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 24, 2025):

This is a known performance issue introduced in 1.10.0 when working with large workflows. The main cause is the new alignment (help-line) feature, which checks all nodes for alignment on every drag event—this adds significant overhead when you have around 100 nodes. The drag logic uses immutable updates and iterates through all nodes, which can cause lag as the node count grows.

A recent optimization was merged (PR #28591) that improves workflow performance: now, noticeable lag only appears with around 200 nodes instead of 50. If you haven't already, try updating to the latest version with this fix. Some lag may still persist with very large workflows, but performance should be much better than before.

If you still experience issues after updating, consider temporarily reducing the number of nodes in a single workflow or profiling with browser dev tools to identify further bottlenecks. The main files involved are web/app/components/workflow/hooks/use-nodes-interactions.ts and use-helpline.ts, where the alignment and drag logic live.

Let me know if the latest update resolves your issue or if you need more details on possible workarounds.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 24, 2025): <!-- Answer --> This is a known performance issue introduced in 1.10.0 when working with large workflows. The main cause is the new alignment (help-line) feature, which checks all nodes for alignment on every drag event—this adds significant overhead when you have around 100 nodes. The drag logic uses immutable updates and iterates through all nodes, which can cause lag as the node count grows. A recent optimization was merged ([PR #28591](https://github.com/langgenius/dify/pull/28591)) that improves workflow performance: now, noticeable lag only appears with around 200 nodes instead of 50. If you haven't already, try updating to the latest version with this fix. Some lag may still persist with very large workflows, but performance should be much better than before. If you still experience issues after updating, consider temporarily reducing the number of nodes in a single workflow or profiling with browser dev tools to identify further bottlenecks. The main files involved are `web/app/components/workflow/hooks/use-nodes-interactions.ts` and `use-helpline.ts`, where the alignment and drag logic live. Let me know if the latest update resolves your issue or if you need more details on possible workarounds. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1ed6bb33-016c-4a90-a6e8-cf8f5bd706fa?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20performance%20issue%20introduced%20in%201.10.0%20when%20working%20with%20large%20workflows.%20The%20main%20cause%20is%20the%20new%20alignment%20%28help-line%29%20feature%2C%20which%20checks%20all%20nodes%20for%20alignment%20on%20every%20drag%20event%E2%80%94this%20adds%20significant%20overhead%20when%20you%20have%20around%20100%20nodes.%20The%20drag%20logic%20uses%20immutable%20updates%20and%20iterates%20through%20all%20nodes%2C%20which%20can%20cause%20lag%20as%20the%20node%20count%20grows.%0A%0AA%20recent%20optimization%20was%20merged%20%28%5BPR%20%2328591%5D%28https%3A//github.com/langgenius/dify/pull/28591%29%29%20that%20improves%20workflow%20performance%3A%20now%2C%20noticeable%20lag%20only%20appears%20with%20around%20200%20nodes%20instead%20of%2050.%20If%20you%20haven%27t%20already%2C%20try%20updating%20to%20the%20latest%20version%20with%20this%20fix.%20Some%20lag%20may%20still%20persist%20with%20very%20large%20workflows%2C%20but%20performance%20should%20be%20much%20better%20than%20before.%0A%0AIf%20you%20still%20experience%20issues%20after%20updating%2C%20consider%20temporarily%20reducing%20the%20number%20of%20nodes%20in%20a%20single%20workflow%20or%20profiling%20with%20browser%20dev%20tools%20to%20identify%20further%20bottlenecks.%20The%20main%20files%20involved%20are%20%60web/app/components/workflow/hooks/use-nodes-interactions.ts%60%20and%20%60use-helpline.ts%60%2C%20where%20the%20alignment%20and%20drag%20logic%20live.%0A%0ALet%20me%20know%20if%20the%20latest%20update%20resolves%20your%20issue%20or%20if%20you%20need%20more%20details%20on%20possible%20workarounds.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28594)
yindo commented 2026-02-21 20:07:47 -05:00
Author
Owner
Copy Link
Copy Source

@lyzno1 commented on GitHub (Nov 24, 2025):

Closes https://github.com/langgenius/dify/pull/28591

@lyzno1 commented on GitHub (Nov 24, 2025): Closes https://github.com/langgenius/dify/pull/28591
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#20514
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?