Skip to content

Instantly share code, notes, and snippets.

@karolsteve

karolsteve/gist:c5e29bdacb25899ae36a3a4f632ae6eb

Forked from bobuss/gist:6515517
Created August 21, 2023 10:27
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save karolsteve/c5e29bdacb25899ae36a3a4f632ae6eb to your computer and use it in GitHub Desktop.
Save karolsteve/c5e29bdacb25899ae36a3a4f632ae6eb to your computer and use it in GitHub Desktop.
Download ZIP
Tuning the Linux Kernel for many tcp connections
Raw
gistfile1.md

(from http://www.metabrew.com/article/a-million-user-comet-application-with-mochiweb-part-1)

Save yourself some time and tune the kernel tcp settings before testing with lots of connections, or your test will fail and you’ll see lots of Out of socket memory messages (and if you are masquerading, nf_conntrack: table full, dropping packet.)

Here are the sysctl settings I ended up with - YMMV, but these will probably do:

$ cat /etc/sysctl.conf
# General gigabit tuning:
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.ipv4.tcp_syncookies = 1
# this gives the kernel more memory for tcp
# which you need with many (100k+) open socket connections
net.ipv4.tcp_mem = 50576   64768   98152
net.core.netdev_max_backlog = 2500
# I was also masquerading the port comet was on, you might not need this
net.ipv4.netfilter.ip_conntrack_max = 1048576

Put these in /etc/sysctl.conf then run sysctl -p to apply them. No need to reboot, now your kernel should be able to handle a lot more open connections, yay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment