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
33 lines
666 B
Text
33 lines
666 B
Text
#
|
|
# tuned configuration
|
|
#
|
|
|
|
[main]
|
|
summary=Optimize for Microsoft SQL Server
|
|
include=throughput-performance
|
|
|
|
[cpu]
|
|
force_latency=5
|
|
|
|
[vm]
|
|
# For multi-instance SQL deployments use 'madvise' instead of 'always'
|
|
transparent_hugepages=always
|
|
dirty_background_bytes=3%
|
|
dirty_bytes=80%
|
|
|
|
[sysctl]
|
|
vm.swappiness=1
|
|
vm.dirty_expire_centisecs=500
|
|
vm.dirty_writeback_centisecs=100
|
|
vm.max_map_count=1600000
|
|
net.core.rmem_default=262144
|
|
net.core.rmem_max=4194304
|
|
net.core.wmem_default=262144
|
|
net.core.wmem_max=1048576
|
|
kernel.numa_balancing=0
|
|
|
|
[scheduler]
|
|
sched_latency_ns=60000000
|
|
sched_migration_cost_ns=500000
|
|
sched_min_granularity_ns=15000000
|
|
sched_wakeup_granularity_ns=2000000
|