-
Notifications
You must be signed in to change notification settings - Fork 874
Description
Hello, I hope you're doing well!
I'm currently working on optimizing 3proxy for high-load usage. I've thoroughly studied the official documentation on the topic (https://3proxy.ru/highload.asp) and have already applied all the recommended settings, from adjusting the ephemeral port range to increasing the ulimit values.
Now, I'm looking into potential network-level optimizations on my Debian system. After some research, I've compiled a list of parameters I’m considering modifying. However, I’m concerned that I might be misunderstanding certain aspects and inadvertently introduce instability.
Would you be able to confirm whether these changes are appropriate, or share any recommendations you might have on this matter?
1- Disabling the reverse path filtering:
net.ipv4.conf.all.rp_filter = 0
net.ipv4.conf.default.rp_filter = 0
2- Enabling tcp_syncookies:
net.ipv4.tcp_syncookies = 1
3- Enabling tcp port reuse:
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_tw_recycle = 0
4- Decreasing the time default value for connections to keep alive:
net.ipv4.tcp_fin_timeout = 15
5- Increasing max conntrack:
net.netfilter.nf_conntrack_max = 524288
6- Optimize the TCP queue:
net.core.somaxconn = 65535
net.core.netdev_max_backlog = 16384
7- Optimize TCP buffer:
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
8- Limit the max TCP socket with TIME_WAIT state:
net.ipv4.tcp_max_tw_buckets = 600000
9- Increasing tcp_max_orphans :
net.ipv4.tcp_max_orphans=65535
10- Increase SYN_RECV TCP connexion waiting list:
net.ipv4.tcp_max_syn_backlog=65535
Thank you very much for your great help 🙏🏼