Introduce Scheduler#load
and Async::Idler
for load shedding and saturation.
#309
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.
Introduce
Scheduler#load
which is a 1-second load average. This load average can be used to detect overload conditions in the event loop. In addition, introduceAsync::Idler
which will schedule tasks up to a givenmaximum_load
.Typical use cases include connection load shedding:
Request load shedding:
And load saturation:
While I'm confident the interface is good enough, there is a small chance that I've not anticipated some critical use case. We may introduce changes to this interface.
Async::Idler
is unlikely to change.Fixes #277.
Types of Changes
Contribution