dify - 💡(How to fix) Fix ifelse node run long time in high-concurrency scenarios [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35704Fetched 2026-04-30 06:45:22
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
1
Author
Timeline (top)
labeled ×2closed ×1commented ×1mentioned ×1
RAW_BUFFERClick to expand / collapse

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.1-fix.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

In high-concurrency scenarios (1000 concurrent users) and serial workflows, the ifelse node takes an exceptionally long time. I scale 30 sandboxes but it didn't work.

<img width="964" height="1056" alt="Image" src="https://github.com/user-attachments/assets/096992c0-a751-4507-9b46-3f7538f02045" />

✔️ Expected Behavior

We expect the runtime of non llm nodes to be less than 300ms.

❌ Actual Behavior

No response

extent analysis

TL;DR

Investigate and optimize the performance of the ifelse node in high-concurrency scenarios and serial workflows.

Guidance

  • Review the ifelse node's implementation to identify potential bottlenecks and areas for optimization.
  • Consider increasing the number of sandboxes or adjusting the scaling strategy to better handle high-concurrency scenarios.
  • Analyze the workflow design to determine if there are opportunities to parallelize tasks or reduce dependencies between nodes.
  • Verify that the expected behavior of non-llm nodes is correctly defined and measured, to ensure accurate comparison with actual behavior.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The issue may be related to the specific implementation of the ifelse node or the workflow design, which is not fully described in the issue. Further investigation and analysis are required to determine the root cause.

Recommendation

Apply workaround: Investigate and optimize the performance of the ifelse node, as the issue is likely related to the node's implementation or the workflow design, rather than a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING