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

Fork Join Parallelism for Workflows #3167

New Issue
Closed
opened 2026-02-21 17:54:36 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:54:36 -05:00
Owner
Copy Link
Copy Source

Originally created by @QuietRocket on GitHub (May 10, 2024).

Self Checks

  • 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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Some workflow configurations have high response latency because they necessitate multiple orthogonal requests to execute sequentially. The latency can be greatly reduced via simple fork-join parallelism. For example, multiple LLM generations in parallel with HTTP requests.

2. Describe the feature you'd like to see

Add Fork and Join blocks.

  • Place a Fork anywhere an LLM/HTTP block could be placed.
  • The output is a series of pathways which can be executed in parallel.
  • In a pathway, only variables defined before the Fork can be accessed.
  • Pathways potentially have a constrained selection of blocks. For example, for chat workflows, "Answer" blocks might need to be disabled since execution order isn't deterministic.
  • In order for the configuration to be valid, all parallel pathways which originate from a Fork must end up in a Join block.
  • Join block waits for all pathways to finish, then continue sequential execution.

3. How will this feature improve your workflow or experience?

Improves response latency by performing orthogonal tasks in parallel.

4. Additional context or comments

image
Fork Join diagram courtesy of this paper.

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @QuietRocket on GitHub (May 10, 2024). ### Self Checks - [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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Some workflow configurations have high response latency because they necessitate multiple orthogonal requests to execute sequentially. The latency can be greatly reduced via simple fork-join parallelism. For example, multiple LLM generations in parallel with HTTP requests. ### 2. Describe the feature you'd like to see Add Fork and Join blocks. - Place a Fork anywhere an LLM/HTTP block could be placed. - The output is a series of pathways which can be executed in parallel. - In a pathway, only variables defined before the Fork can be accessed. - Pathways potentially have a constrained selection of blocks. For example, for chat workflows, "Answer" blocks might need to be disabled since execution order isn't deterministic. - In order for the configuration to be valid, all parallel pathways which originate from a Fork must end up in a Join block. - Join block waits for all pathways to finish, then continue sequential execution. ### 3. How will this feature improve your workflow or experience? Improves response latency by performing orthogonal tasks in parallel. ### 4. Additional context or comments ![image](https://github.com/langgenius/dify/assets/56984521/d8177f68-aa3e-4e30-b3bd-a132f734a05b) Fork Join diagram courtesy of [this paper](https://www.researchgate.net/figure/The-fork-join-model-used-for-thread-level-parallelism-in-OpenMP_fig2_305806654). ### 5. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 17:54:36 -05:00
yindo closed this issue 2026-02-21 17:54:36 -05:00
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 💪 enhancement
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#3167
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?