Ability to Limit the Number of Scrapers Running Concurrently #1664
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
|
Did you mean string or integer for the env variable? Thanks for adding this :D |
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.
Fixes #1626
This allows users to specify the maximum number of scrapers that can run concurrently. It can be set with the Environment Variable CONCURRENT_SCRAPERS or runtime parameter concurrent_scrapers.
Note: it will run the scrapers in batches, all scrapers in the batch must complete before it will start the next batch, ie if you set the number of scrapers to 10 and 10 are been scraped and one scraper finishes another scraper will not start, all 10 must finish then another 10 will start