GitHub user PG1204 added a comment to the discussion: RFC: Workflow Performance Profiler - full design & implementation walkthrough
@chenlica Just to clarify, the profiler isn't an operator. It's a workflow-level analysis feature that sits on top of any existing workflow: it reads the per-operator runtime statistics that Amber already emits and paints the canvas as a heatmap. The profiler would work the same way regardless of which operators are present in the workflow. Would either of these visuals work for you instead? - A screenshot/diagram of a sample workflow that uses several HuggingFace operators, with the profiler heatmap turned on showing which operator is the bottleneck and also show the optimization hints. - A flow diagram of the profiler's internal data pipeline (OperatorStatisticsUpdateEvent → WorkflowStatusService → ProfilerService → JointJS heatmap + hints panel + agent tools). Happy to put either (or both) together. GitHub link: https://github.com/apache/texera/discussions/5216#discussioncomment-17130314 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
