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

Workflow Performance Analytics & Optimization System #20659

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

Originally created by @jworth008 on GitHub (Nov 28, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Yes, this addresses a critical gap in Dify's current capabilities. Users and developers face significant challenges:

Current Pain Points:

  • No visibility into workflow performance: Users cannot identify which nodes are slow or causing bottlenecks
  • Manual optimization is time-consuming: Developers must manually analyze logs and metrics to optimize workflows
  • Cost blindness: No insights into LLM token usage and costs, leading to unexpected expenses
  • Repeated work: No caching mechanism means the same operations are executed repeatedly, wasting time and money
  • Reliability issues: No systematic way to identify and fix failure patterns or excessive retries
  • No data-driven decisions: Users lack metrics to make informed optimization choices

Real-World Impact:

  • Enterprise users report workflows taking 10-30 seconds when they could be 2-5 seconds with caching
  • LLM token costs are 30-50% higher than necessary due to lack of optimization insights
  • Support teams spend significant time helping users troubleshoot performance issues
  • Users are considering competitors that offer better observability

User Stories:

"I have a workflow that calls an LLM node with the same prompt repeatedly, but I have no way to cache the results. This costs me $50/month in unnecessary API calls." - Enterprise User

"My workflow is slow but I don't know which node is the bottleneck. I need performance metrics to optimize it." - Developer

"I want to reduce my token costs but I don't have visibility into which nodes are consuming the most tokens." - Startup Founder

2. Additional context or comments

Proposed Solution

Implement a comprehensive Workflow Performance Analytics & Optimization System with three core components:

1. Performance Tracking & Profiling

  • Track workflow-level metrics (execution time, success rates, token usage, costs)
  • Profile node-level performance (individual node execution times, resource usage)
  • Identify bottlenecks automatically with severity classification
  • Provide historical trend analysis

2. Intelligent Caching Layer

  • Automatically cache deterministic node results
  • Configurable TTL by node type (LLM: 24h, Code: 7d, HTTP: 1h, etc.)
  • Smart cache invalidation strategies
  • Track cache performance (hit rates, time saved, storage usage)

3. AI-Powered Optimization Advisor

  • Analyze workflow execution patterns
  • Generate evidence-based recommendations across 6 categories:
    • Performance: Caching opportunities, parallelization, bottleneck fixes
    • Cost: Token optimization, API call reduction
    • Reliability: Error pattern detection, retry optimization
    • Scalability: Resource usage optimization
    • Best Practices: Code quality, configuration improvements
    • Parallelization: Independent node identification

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @jworth008 on GitHub (Nov 28, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Yes, this addresses a critical gap in Dify's current capabilities. Users and developers face significant challenges: **Current Pain Points:** - **No visibility into workflow performance**: Users cannot identify which nodes are slow or causing bottlenecks - **Manual optimization is time-consuming**: Developers must manually analyze logs and metrics to optimize workflows - **Cost blindness**: No insights into LLM token usage and costs, leading to unexpected expenses - **Repeated work**: No caching mechanism means the same operations are executed repeatedly, wasting time and money - **Reliability issues**: No systematic way to identify and fix failure patterns or excessive retries - **No data-driven decisions**: Users lack metrics to make informed optimization choices **Real-World Impact:** - Enterprise users report workflows taking 10-30 seconds when they could be 2-5 seconds with caching - LLM token costs are 30-50% higher than necessary due to lack of optimization insights - Support teams spend significant time helping users troubleshoot performance issues - Users are considering competitors that offer better observability **User Stories:** > "I have a workflow that calls an LLM node with the same prompt repeatedly, but I have no way to cache the results. This costs me $50/month in unnecessary API calls." - Enterprise User > "My workflow is slow but I don't know which node is the bottleneck. I need performance metrics to optimize it." - Developer > "I want to reduce my token costs but I don't have visibility into which nodes are consuming the most tokens." - Startup Founder ### 2. Additional context or comments ### Proposed Solution Implement a comprehensive **Workflow Performance Analytics & Optimization System** with three core components: #### 1. Performance Tracking & Profiling - Track workflow-level metrics (execution time, success rates, token usage, costs) - Profile node-level performance (individual node execution times, resource usage) - Identify bottlenecks automatically with severity classification - Provide historical trend analysis #### 2. Intelligent Caching Layer - Automatically cache deterministic node results - Configurable TTL by node type (LLM: 24h, Code: 7d, HTTP: 1h, etc.) - Smart cache invalidation strategies - Track cache performance (hit rates, time saved, storage usage) #### 3. AI-Powered Optimization Advisor - Analyze workflow execution patterns - Generate evidence-based recommendations across 6 categories: - **Performance**: Caching opportunities, parallelization, bottleneck fixes - **Cost**: Token optimization, API call reduction - **Reliability**: Error pattern detection, retry optimization - **Scalability**: Resource usage optimization - **Best Practices**: Code quality, configuration improvements - **Parallelization**: Independent node identification ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:08:21 -05:00
yindo closed this issue 2026-02-21 20:08:21 -05:00
yindo commented 2026-02-21 20:08:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 29, 2025):

Hi, @hsparks-codes. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You proposed adding a Workflow Performance Analytics & Optimization System to address workflow bottlenecks, high LLM token costs, and caching issues.
  • The system would provide performance metrics, cost insights, and reliability improvements.
  • The goal is to help users and developers optimize workflows to save time and reduce expenses.
  • There has been no further activity or discussion on this proposal since it was opened.

Next Steps:

  • Please let me know if this feature is still relevant to your needs and the latest version of Dify by commenting on this issue.
  • If I don’t hear back within 15 days, I will automatically close this issue to keep the backlog manageable.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 29, 2025): Hi, @hsparks-codes. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You proposed adding a Workflow Performance Analytics & Optimization System to address workflow bottlenecks, high LLM token costs, and caching issues. - The system would provide performance metrics, cost insights, and reliability improvements. - The goal is to help users and developers optimize workflows to save time and reduce expenses. - There has been no further activity or discussion on this proposal since it was opened. **Next Steps:** - Please let me know if this feature is still relevant to your needs and the latest version of Dify by commenting on this issue. - If I don’t hear back within 15 days, I will automatically close this issue to keep the backlog manageable. Thanks for your understanding and contribution!
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#20659
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?