Respect telemetry.collection_interval to reduce cpu churn when running many containers #130
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
lgfa29
approved these changes
Aug 10, 2021
towe75
force-pushed
the
f_collection_interval
branch
from
50b0f8c to
dc22a4b
Compare
|
before this I found my podman socket daemon flooded by health check log. I have to increase podman log level to |
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.
Use telemetry.collection_interval for each container monitor. Previously we polled for each container with a very fast, static, 1 second interval. This does not scale very well and we can see a considerable load on the podman service when running e.g. a job with 30 pause containers.