GitHub user PG1204 edited a comment on the discussion: RFC: Workflow Performance Profiler - full design & implementation walkthrough
> My suggestion would be to land the heatmap first and handle the hints as a > separate issue, where we can reason why each rule exists, where its > thresholds come from, and which hint to show when several fire at once. Agreed, this lines up with @Yicong-Huang's earlier proposal: umbrella issue "workflow runtime performance visualization" with sub-issues for (1) WorkflowStatusService refactor, (2) heatmap overlay, (3) persistence. Hints weren't in those three; they slot in naturally as future sub-issues which will be covering rule motivation, threshold justification, and conflict/dedup policy , landing only after the foundation is in. I can open the umbrella + sub-issues 1 to 3 first upon the team's approval, hints sub-issue can follow later after thorough discussion. Thanks for the push. GitHub link: https://github.com/apache/texera/discussions/5216#discussioncomment-17285751 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
