feat: Elevate non-LLM concurrency limits to RunConfig
#242
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Previously, the value of
MAX_CONCURRENCY_PER_NON_LLM_GENERATORwas hard-coded into the library. This hardcoding creates a problem when a plugin (or other task definition) inherits fromColumnGeneratorCellByCell. I this case, there was presently no way to control concurrency up or down. We saw this leading to severe performance degradations for some implementations.This PR does not yet address the root-cause (an under-defined resource-management system with respect to sub-task execution), however it does remove a blocker by bringing this parameter up to the
RunConfig.Changes
RunConfigwith newnon_llm_max_parallel_workers.RunConfigis put in code references.RunConfigat runtime.