GitHub user PG1204 added a comment to the discussion: RFC: Workflow Performance
Profiler - full design & implementation walkthrough
> My general comment is that visual diagrams can make your design easier to
> understand. Maybe you can add both diagrams then we can decide?
```mermaid
flowchart TD
A[Execution Engine<br/><i>unchanged</i>]
-->|OperatorStatisticsUpdateEvent<br/>over existing websocket|
B[WorkflowStatusService<br/><i>existing</i>]
B -->|getStatusUpdateStream<br/>throttled 500ms|
C[ProfilerService<br/><b>new</b><br/>reactive state]
C --> D[profiler-config<br/>WorkflowContent round-trip]
C --> E[profiler-hints<br/>6-rule engine]
C --> F[profiler-delta<br/>baseline diff]
C --> G[profiler-history<br/>server-fetched runs]
C --> H[profiler-report<br/>MD + JSON export]
C --> I[profiler-suggestions<br/><i>optional</i> ghost overlays]
D --> UI
E --> UI
F --> UI
G --> UI
H --> UI
I --> UI
UI[UI Integration<br/>joint-ui · menu · property-panel · workflow-editor]
classDef existing fill:#e8e8e8,stroke:#888,color:#333
classDef new fill:#d4edda,stroke:#28a745,color:#155724
classDef optional fill:#fff3cd,stroke:#856404,color:#856404
classDef ui fill:#cce5ff,stroke:#004085,color:#004085
class A,B existing
class C,D,E,F,G,H new
class I optional
class UI ui
```
Profiler data flow. Gray = existing Texera, green = new modules, yellow =
optional, blue = UI integration points. All new code lives under
frontend/src/app/workspace/service/profiler/ (plus the optional
ProfilerScoring.scala helper). No new event types on the wire, no engine
changes.
GitHub link:
https://github.com/apache/texera/discussions/5216#discussioncomment-17212801
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
