Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature]: Discuss/Design Parallelization / Options for Sub Workflows #783

Open
srichmond opened this issue Dec 4, 2024 · 1 comment
Open

[Feature]: Discuss/Design Parallelization / Options for Sub Workflows #783

srichmond opened this issue Dec 4, 2024 · 1 comment
Labels
code sprint ticket Berkeley visit feature Request for new feature triage Issue that need to be triaged

Comments

@srichmond
Copy link
Contributor

Contact Details

[email protected]

What should we build?

We would like to discuss what options are available to implement parallelization for workflows and possibly sub workflows

Relevant pseudo code

No response
@srichmond srichmond added feature Request for new feature triage Issue that need to be triaged code sprint ticket Berkeley visit labels Dec 4, 2024
@spinoshi
Copy link
Contributor

Use-cases:

  • performance increase without losing papertrail

  • migration of subscriptions with insisting subscriptions on top that need to be migrated.

  • what if one sub-workflow fails? you just retry it. (one thread out of four)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code sprint ticket Berkeley visit feature Request for new feature triage Issue that need to be triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@srichmond @spinoshi