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] Update ProcessNode to use the plugin's thread pool #366

Closed
dbwiddis opened this issue Jan 5, 2024 · 0 comments · Fixed by #374
Closed

[FEATURE] Update ProcessNode to use the plugin's thread pool #366

dbwiddis opened this issue Jan 5, 2024 · 0 comments · Fixed by #374
Assignees
@dbwiddis
Labels
enhancement New feature or request performance Make it fast! v2.12.0

Comments

@dbwiddis
Copy link
Member

dbwiddis commented Jan 5, 2024

Is your feature request related to a problem?

The ProcessNode execution of workflow steps is using the Generic thread pool.

While this iteration moves quickly, we should keep all our workflow actions in our own thread pool.

What solution would you like?

Use the plugin's thread pool for the step execution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dbwiddis dbwiddis

Labels
enhancement New feature or request performance Make it fast! v2.12.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use provisioning thread pool in Process Node dbwiddis/flow-framework
1 participant
@dbwiddis