Parameterization of Max Workers in ResourceManager #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@migueldl96 thanks so much for the contribution! Apologies I didn't see this for a few days. I'm merging this in and will publish a patch update for the library shortly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a parameterization feature for the ResourceManager class, allowing the number of maximum workers (max_workers) to be specified during the instantiation of the class. The addition of the max_workers parameter in the init method enables greater flexibility in configuring the concurrent execution environment. With this enhancement, users can now initialize the ResourceManager with a custom number of maximum workers, providing more control over the concurrent processing capabilities of the application.