This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
add a short sleep in the supervisor's event loop to reduce CPU usage #1080
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
|
Note, this is based off of #1078 , which should be merged before this PR. The only file with changes unique to this PR is |
ranweiler
approved these changes
Jul 16, 2021
chkeita
approved these changes
Jul 16, 2021
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Without this sleep, once the
Agent.runloop is in thebusystate, it is turned into a tight loop callingwait4of the running agents. This sleep adds a small window to allow the rest of the system to work. Empirical testing shows this has a significant reduction in CPU use.This sleep should be removed once the
worker_runnermonitoring is turned into something event driven.