External/sysctl
1
0
Fork 0
mirror of https://github.com/k4yt3x/sysctl.git synced 2025-12-23 12:46:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

Disable TCP slow start after idle

Browse Source 
Signed-off-by: IceCodeNew <32576256+IceCodeNew@users.noreply.github.com>
This commit is contained in:
IceCodeNew 2021-10-12 21:16:55 +08:00
parent 3ea204497d
commit 2ead2cea26
No known key found for this signature in database
GPG Key ID: B46F760A59127A64
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
sysctl.conf
View File

@ -215,6 +215,15 @@ net.ipv4.ip_local_port_range = 1024 65535
# - 2: enable timestamps without random offsets # - 2: enable timestamps without random offsets
net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_timestamps = 0
# Refer to: https://dropbox.tech/infrastructure/optimizing-web-servers-for-high-throughput-and-low-latency
# the main problem with slowstart after idle is that “idle” is defined as one RTO, which is too small.
# Refer to: https://hpbn.co/building-blocks-of-tcp/#slow-start-restart
# Not surprisingly, SSR can have a significant impact on performance of long-lived TCP connections that may idle for bursts of time — e.g., due to user inactivity.
# As a result, it is generally recommended to disable SSR on the server to help improve performance of long-lived HTTP connections.
# Refer to: https://github.com/httpwg/http2-spec/wiki/Ops
# This drops cwnd back down to initcwnd and goes back to slow start after the connection has been “idle” (defined as the RTO). This kills persistent single connection performance and should be turned off.
net.ipv4.tcp_slow_start_after_idle = 0
# enabling SACK can increase the throughput # enabling SACK can increase the throughput
# but SACK is commonly exploited and rarely used # but SACK is commonly exploited and rarely used
net.ipv4.tcp_sack = 0 net.ipv4.tcp_sack = 0