#

[0] Fix | Delete

# tuned configuration

[1] Fix | Delete

#

[2] Fix | Delete

[3] Fix | Delete

[main]

[4] Fix | Delete

summary=Optimize for running inside a virtual guest

[5] Fix | Delete

include=throughput-performance

[6] Fix | Delete

[7] Fix | Delete

[sysctl]

[8] Fix | Delete

# If a workload mostly uses anonymous memory and it hits this limit, the entire

[9] Fix | Delete

# working set is buffered for I/O, and any more write buffering would require

[10] Fix | Delete

# swapping, so it's time to throttle writes until I/O can catch up. Workloads

[11] Fix | Delete

# that mostly use file mappings may be able to use even higher values.

[12] Fix | Delete

#

[13] Fix | Delete

# The generator of dirty data starts writeback at this percentage (system default

[14] Fix | Delete

# is 20%)

[15] Fix | Delete

vm.dirty_ratio = 30

[16] Fix | Delete

[17] Fix | Delete

# Filesystem I/O is usually much more efficient than swapping, so try to keep

[18] Fix | Delete

# swapping low. It's usually safe to go even lower than this on systems with

[19] Fix | Delete

# server-grade storage.

[20] Fix | Delete

vm.swappiness = 30

[21] Fix | Delete

[22] Fix | Delete