Skip to content

feat(backend): Support flow control (backpressure) visualization in backend and frontend#4270

Draft
yunyad wants to merge 7 commits intoapache:mainfrom
yunyad:yunyad-flow-control-vis
Draft

feat(backend): Support flow control (backpressure) visualization in backend and frontend#4270
yunyad wants to merge 7 commits intoapache:mainfrom
yunyad:yunyad-flow-control-vis

Conversation

@yunyad
Copy link
Contributor

@yunyad yunyad commented Mar 7, 2026

What changes were proposed in this PR?

This PR introduces backend support for flow control (backpressure) visualization in workflow execution.

During workflow execution, operators may experience backpressure when they receive data faster than they can process. In such cases, the operator signals its upstream operators to temporarily slow down or pause data transmission. This mechanism helps prevent buffer overflow and maintains stable execution.

This PR exposes the backpressure status of operators and edges from the backend so that the frontend can visualize the flow control behavior of the workflow.

The main changes include:

  • Adding backend support to collect and propagate flow control / backpressure status
  • Extending execution monitoring data structures to include flow control information

Any related issues, documentation, discussions?

How was this PR tested?

Was this PR authored or co-authored using generative AI tooling?

@yunyad yunyad self-assigned this Mar 7, 2026
@github-actions github-actions bot added engine python frontend Changes related to the frontend GUI labels Mar 7, 2026
@yunyad yunyad marked this pull request as draft March 7, 2026 21:32
@yunyad yunyad changed the title feat(backend): flow control visualization feat(backend): Support flow control (backpressure) visualization in backend and frontend Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

engine frontend Changes related to the frontend GUI python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant