Disable dynamic tuning by default #430
Open
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
Dynamic tuning is counterproductiv in general: HW should be set in the correct state statically, dynamic wake-ups and adjustings cost performance and power and should only apply in specific scenarios. On recent Intel CPUS: (e.g. Gold 5115 CPU @ 2.40GHz, Silver 4110 CPU @ 2.10GHz) CPU family: 6 Model: 85 Stepping: 4 when utilizing one CPU core (cat /dev/null >/dev/zero &) The CPU load calculated by the cpu plugin exceeds and latency_low options apply: self._set_latency(instance.options["latency_low"]) Latency limit is that low, that lower C-states are not entered anymore and CPU cores cannot enter Turbo modes, due to CPU socket thermal restrictions. Therefore, the utilized CPU core is processing data slower, even tuned set "low_latency" settings AND power consumption is increased as well.
|
@yarda I have heard that tuned plans to turn dynamic tuning off by default. When will this change occur? It'd be nice to have this off by default. Thanks! |
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.
Dynamic tuning is counterproductiv in general:
HW should be set in the correct state statically, dynamic wake-ups and adjustings
cost performance and power and should only apply in specific scenarios.
On recent Intel CPUS:
(e.g. Gold 5115 CPU @ 2.40GHz, Silver 4110 CPU @ 2.10GHz)
CPU family: 6
Model: 85
Stepping: 4
when utilizing one CPU core (cat /dev/null >/dev/zero &)
The CPU load calculated by the cpu plugin exceeds and latency_low
options apply:
self._set_latency(instance.options["latency_low"])
Latency limit is that low, that lower C-states are not entered anymore
and CPU cores cannot enter Turbo modes, due to CPU socket thermal
restrictions.
Therefore, the utilized CPU core is processing data slower, even
tuned set "low_latency" settings AND power consumption is increased as well.