Same for dirty_background_ratio and dirty_background_bytes. Using both the ratio and the bytes is not compatible with the current profile inheritance implementation, because it is not possible for dirty_bytes in a child profile to override dirty_ratio in its parent profile. Resolves: RHEL-101578
16 lines
325 B
Text
16 lines
325 B
Text
#
|
|
# tuned configuration
|
|
#
|
|
|
|
[main]
|
|
summary=Optimize for running KVM guests
|
|
include=throughput-performance
|
|
|
|
[vm]
|
|
# Start background writeback (via writeback threads) at this percentage (system
|
|
# default is 10%)
|
|
dirty_background_bytes = 5%
|
|
|
|
[cpu]
|
|
# Setting C3 state sleep mode/power savings
|
|
force_latency=cstate.id_no_zero:3|70
|