Skip to content

Use Workpool for actions: enables retries & parallelism limits #30

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.

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

Merged
merged 51 commits into from
Apr 5, 2025

Conversation

ianmacartney
Copy link
Contributor

@ianmacartney ianmacartney commented Apr 2, 2025

Use the Workpool internally to handle durable action execution with retries

Fixes #7
Fixes #8
Fixes #18
Fixes #31
Fixes #24

@ianmacartney ianmacartney marked this pull request as ready for review April 4, 2025 03:02
@ianmacartney ianmacartney requested a review from sujayakar April 4, 2025 03:02
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything is reactive?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meaning, you might want to highlight that benefit... it's obvious if you know convex, but reinforcing that idea here.

README.md Outdated
### Specifying how many workflows can run in parallel

You can specify how many workflows can run in parallel by setting the `maxParallelism`
workpool option. This defaults to 50.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this more than can actually run on the free plan?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll drop it to 25. Each of q/m/a/node action get 16. But on the free plan I suspect you won't struggle with huge scheduler backlog (and the scheduler is fair enough that you'll make progress, even if each new scheduler task might be behind 9 workflow tasks in the queue). lmk if you think a different default makes sense, but I don't want Pro customers to think it's slow by default b/c of throughput limits.

@ianmacartney ianmacartney merged commit 993db3a into main Apr 5, 2025
1 check passed
@ianmacartney ianmacartney deleted the ian/workpool branch April 5, 2025 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants