Skip to content

Optimizing Shadowsocks

clowwindy edited this page Jun 16, 2014 · 23 revisions

On Debian 7:

Create /etc/sysctl.d/local.conf with the following content:

fs.file-max = 51200

net.core.rmem_max = 67108864 
net.core.wmem_max = 67108864 
net.core.netdev_max_backlog = 250000
net.core.somaxconn = 3240000

net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 0
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_keepalive_time = 1200
net.ipv4.ip_local_port_range = 10000 65000
net.ipv4.tcp_max_syn_backlog = 8192
net.ipv4.tcp_max_tw_buckets = 5000
net.ipv4.tcp_fastopen = 3
net.ipv4.tcp_rmem = 4096 87380 67108864
net.ipv4.tcp_wmem = 4096 65536 67108864
net.ipv4.tcp_mtu_probing = 1
net.ipv4.tcp_congestion_control = hybla

Then:

sysctl --system

Warning: DO NOT ENABLE net.ipv4.tcp_tw_recycle!!! See this article.

After optimizing, Shadowsocks should be able to handle thousands of connections with about 20MB memory and < 10% CPU.

if_eth0-day

fw_conntrack-day

cpu-day