Stepped Burst Load Strategy #1
Merged
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
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 adds a stepped burst load strategy, which enqueues an increasing (or decreasing) burst of tasks in a stepwise manner, regardless of how many might already be running.
i.e. passing
(step: 10, from: 10, to: 50, interval: TimeSpan.FromSeconds(1))will enqueue 10 tasks, then 20 tasks one second later, then 30 one second after that, then 40, then 50, and stop, for a total of 150 tasks. If step is negative, you can go from high to low values.This also improves some member names to avoid ambiguity and help be more consistent across types, upgrades NuGet packages, and turns on warnings as errors.