Workflow Activity code is directly run via DurableTaskGrpcWorker #1331
Description
This worker initialises a single thread responsible for executing both activity and workflow code by fetching tasks from the sidecar. However, this design leads to a bottleneck: if a long-running activity is encountered, the thread becomes blocked, preventing the execution of other activities or workflows.
However, this design leads to a bottleneck: if a long-running activity is encountered, the thread becomes blocked, preventing the execution of other activities or workflows
Ideally, the activity code should not execute on the same thread used for task fetching. Instead, a thread pool should be used to offload activity execution, allowing the main thread to continue retrieving new jobs from the sidecar.
Metadata
Metadata
Assignees
Labels
No labels