ccff8454de
AWS Nitro instances need special tuning for NVMe devices: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html#timeout-nvme-ebs-volumes [sysfs] /sys/module/nvme_core/parameters/io_timeout=4294967295 /sys/module/nvme_core/parameters/max_retries=10 This tuning should probably be moved to Cloud Provider-specific profiles once the functionality is implemented. Signed-off-by: Jiri Mencak <jmencak@users.noreply.github.com>
36 lines
896 B
Text
36 lines
896 B
Text
#
|
|
# tuned configuration
|
|
#
|
|
|
|
[main]
|
|
summary=Optimize systems running OpenShift (parent profile)
|
|
include=${f:virt_check:virtual-guest:throughput-performance}
|
|
|
|
[selinux]
|
|
avc_cache_threshold=8192
|
|
|
|
[net]
|
|
nf_conntrack_hashsize=1048576
|
|
|
|
[sysctl]
|
|
net.ipv4.ip_forward=1
|
|
kernel.pid_max=>4194304
|
|
net.netfilter.nf_conntrack_max=1048576
|
|
net.ipv4.conf.all.arp_announce=2
|
|
net.ipv4.neigh.default.gc_thresh1=8192
|
|
net.ipv4.neigh.default.gc_thresh2=32768
|
|
net.ipv4.neigh.default.gc_thresh3=65536
|
|
net.ipv6.neigh.default.gc_thresh1=8192
|
|
net.ipv6.neigh.default.gc_thresh2=32768
|
|
net.ipv6.neigh.default.gc_thresh3=65536
|
|
vm.max_map_count=262144
|
|
|
|
[sysfs]
|
|
/sys/module/nvme_core/parameters/io_timeout=4294967295
|
|
/sys/module/nvme_core/parameters/max_retries=10
|
|
|
|
[scheduler]
|
|
# see rhbz#1979352; exclude containers from aligning to house keeping CPUs
|
|
cgroup_ps_blacklist=/kubepods\.slice/
|
|
# workaround for rhbz#1921738
|
|
runtime=0
|