howtos:sysctl
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | howtos:sysctl [02/12/2018 21:34] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | # 256 KB default performs well experimentally, | ||
+ | net.core.rmem_default = 262144 | ||
+ | net.core.wmem_default = 262144 | ||
+ | # When opening a high-bandwidth connection while the receiving end is under | ||
+ | # memory pressure, disk I/O may be necessary to free memory for the socket, | ||
+ | # making disk latency the effective latency for the bandwidth-delay product | ||
+ | # initially. | ||
+ | # to account for overhead, to ensure that new sockets can saturate the medium | ||
+ | # quickly. | ||
+ | net.core.rmem_max = 8388608 | ||
+ | net.core.wmem_max = 8388608 | ||
+ | |||
+ | # Allow a deep backlog for 10 Gb and bonded Gb ethernet connections | ||
+ | net.core.netdev_max_backlog = 10000 | ||
+ | |||
+ | # Always have one page available, plus an extra for overhead, to ensure TCP NFS | ||
+ | # pageout doesn' | ||
+ | # plus overhead for rmem, since most LAN sockets won't need to scale. | ||
+ | net.ipv4.tcp_rmem = 8192 87380 8388608 | ||
+ | net.ipv4.tcp_wmem = 8192 65536 8388608 | ||
+ | |||
+ | # Always have enough memory available on a UDP socket for an 8k NFS request, | ||
+ | # plus overhead, to prevent NFS stalling under memory pressure. | ||
+ | # low enough that memory fragmentation is unlikely to cause problems. | ||
+ | net.ipv4.udp_rmem_min = 16384 | ||
+ | net.ipv4.udp_wmem_min = 16384 | ||
+ | |||
+ | # Ensure there' | ||
+ | # socket. | ||
+ | net.ipv4.tcp_mem = 8388608 12582912 16777216 | ||
+ | net.ipv4.udp_mem = 8388608 12582912 16777216 | ||
+ | </ |
howtos/sysctl.txt · Last modified: 02/12/2018 21:34 by 127.0.0.1