096c402881
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
23 lines
752 B
Text
23 lines
752 B
Text
#
|
|
# tuned configuration
|
|
#
|
|
|
|
[main]
|
|
summary=Optimize for running inside a virtual guest
|
|
include=throughput-performance
|
|
|
|
[vm]
|
|
# If a workload mostly uses anonymous memory and it hits this limit, the entire
|
|
# working set is buffered for I/O, and any more write buffering would require
|
|
# swapping, so it's time to throttle writes until I/O can catch up. Workloads
|
|
# that mostly use file mappings may be able to use even higher values.
|
|
#
|
|
# The generator of dirty data starts writeback at this percentage (system default
|
|
# is 20%)
|
|
dirty_bytes = 30%
|
|
|
|
[sysctl]
|
|
# Filesystem I/O is usually much more efficient than swapping, so try to keep
|
|
# swapping low. It's usually safe to go even lower than this on systems with
|
|
# server-grade storage.
|
|
vm.swappiness = 30
|