4 ms·
Interesting post, thanks for sharing! About the suggested sysctl.conf settings: I think you'd also need to adjust net.core.rmem_max and net.core.wmem_max in or
by metachris 16y ago
Interesting post, thanks for sharing!
About the suggested sysctl.conf settings: I think you'd also need to adjust net.core.rmem_max and net.core.wmem_max in order for the net.ipv4.tcp_rmem and net.ipv4.tcp_wmem settings to be effective.
Furthermore it couldn't hurt to increase net.core.netdev_max_backlog, which is the maximum number of packets queued on the input side, when the interface receives packets faster than kernel can process them.
- superjared 16y agoRegarding the `net.core` parameters. We do modify those, but my assumption (probably wrong) was that the `net.ipv4` changes would override the core configs. I'll take a look and update the post. Good point about `netdev_max_backlog`, I need to read up on that one too. Thanks for the feedback!
- metachris 16y agoI'm playing around with the exact same things -- maximum concurrent tcp sockets on Amazon EC2 large instances. How many did you get running?
- robotadam 16y agoWe got over 500k/instance: http://blog.urbanairship.com/blog/2010/08/24/c500k-in-action-at-urban-airship/ http://blog.urbanairship.com/blog/2010/08/24/c500k-in-action...
- superjared 16y agoOn an EC2 Large we hit 520K.