tuned-main.conf(5) tuned-main.conf file format description tuned-main.conf(5)NAME
tuned-main.conf - Tuned global configuration file
SYNOPSIS
/etc/tuned/tuned-main.conf
DESCRIPTION
This man page documents format of the Tuned global configuration file. The tuned-main.conf file uses the ini-file format.
dynamic_tuning=BOOL
This defines whether the dynamic tuning is enabled. It is boolean value. It can be True or 1 if the dynamic tuning is enabled and
False or 0 if disabled. In such case only the static tuning will be used. Please note if it is enabled here, it is still possible to
individually disable it in plugins.
sleep_interval=INT
Tuned daemon is periodically waken after INT seconds and checks for events. By default this is set to 1 second. If you have Python 2
interpreter with applied patch from Red Hat Bugzilla #917709 this controls responsiveness time of Tuned to commands (i.e. if you
request profile switch, it may take up to 1 second until Tuned reacts). Increase this number for higher responsiveness times and
more power savings (due to lower number of wakeups). In case you have unpatched Python 2 interpreter, this settings will have no
visible effect, because the intepreter will poll 20 times per second.
update_interval=INT
Update interval for dynamic tuning (in seconds). Tuned daemon is periodically waken after INT seconds, updates its monitors, calcu-
lates new tuning parameters for enabled plugins and applies the changes. Plugins that have disabled dynamic tuning are not pro-
cessed. By default the INT is set to 10 seconds. Tuned daemon doesn't periodically wake if dynamic tuning is globally disabled (see
dynamic_tuning) or this setting set to 0. This must be multiple of sleep_interval.
EXAMPLE
dynamic_tuning = 1
sleep_interval = 1
update_interval = 10
FILES
/etc/tuned/tuned-main.conf
SEE ALSO tuned(8)AUTHOR
Written by Jaroslav karvada <jskarvad@redhat.com>.
REPORTING BUGS
Report bugs to <power-management@lists.fedoraproject.org>.
Jaroslav karvada 15 Oct 2013 tuned-main.conf(5)
Check Out this Related Man Page
loratune(1M)loratune(1M)NAME
loratune - initiate LORA tuneup to improve alignment of processing resources
SYNOPSIS DESCRIPTION
The command improves the performance of an HP-UX system in LORA (Locality-Optimizated Resource Alignment) mode, by triggering the kernel to
do optimization tuning of the system and application memory.
The command may return before the tuning is complete. This tuning can continue in the background for several minutes after the command
returns. If the command is interrupted, or the command process is otherwise terminated, no subsequent tuning operations will be initiated,
but those in progress will continue until completion.
When no options are specified, all locality domains are tuned.
Options
This option limits the tuning to the locality domain specified by
lid.
Application Usage
In Locality-Optimized Resource Alignment (LORA) mode, performance of applications may improve when their processors and the memory that
they use are aligned in the same locality. The HP-UX kernel attempts to maintain such alignment at all times, but it is possible for mis-
alignment to occur when the system workload transitions significantly. If that happens, the command can be used to reestablish alignment
and improve application performance.
Here are some examples of workload transition events that may cause misalignment of processing resources:
o Starting or terminating an application that consumes a large amount of processor or memory resources.
o The workload demand surges far above the normal level and then recedes.
o Dynamic platform operations that add or subtract processor or memory resources from the operating system's control.
If one of those events has occurred, and application performance is not as high as it can be, then it is appropriate to invoke the command.
RETURN VALUES
The command returns a 0 when successful, and a non-zero value when unsuccessful.
ERRORS
The command will not initiate any tuning and will return a non-zero value if the user does not have appropriate privilege.
WARNINGS
The command can consume a significant amount of system processing resources to restore optimal alignment. Ideally, the command should be
invoked prior to the time when performance is critical, not during the time when performance is critical. The command should be invoked
after the workload transition is complete, not during workload transition. Although tuning can continue in the background for several min-
utes, it is not necessary to wait any more than five minutes between invoking the command and launching new applications.
EXAMPLES
If eight instances of SAP were running in localities with locality domain identifiers 4 and 5, and four of those instances were shut down,
then it would be appropriate to tuneup the remaining four instances. An example command would be:
If an HP-UX system in LORA mode had one of its cells deactivated, then it would be appropriate to tuneup the entire system. An example
command would be:
AUTHOR
was developed by HP.
SEE ALSO mpsched(1), numa_policy(5), lora(7).
Itanium(R)-based Systems Only loratune(1M)