allow load per cpu option to be optional #344
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
xp-1000
force-pushed
the
load_per_cpu_optional
branch
from
617f8b4
to
a56a067
Compare
xp-1000
added
detectors
xp-1000
requested review from
BzSpi,
cvauvarin,
Shr3ps and
tchernomax
as code owners
Poil
approved these changes
Nov 16, 2021
xp-1000
force-pushed
the
load_per_cpu_optional
branch
from
1583bba
to
0bccabf
Compare
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.
the load monitor from smart agent allows to define
perCPUoption to automatically average load per cpu number.before this was a mandatory config to set to use the load detector properly, it provides some advantages:
that said, in some cases it could be useful to keep the original/raw information and make the division into the signalflow instead.
This PR adds an option to make this possible.