Yes<br><br>fs.file-max = 65535<br> <br>James<br> <br><br>On Mon, Mar 8, 2010 at 2:21 PM, powderhound <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>> wrote:<br>><br>> > When I run the benchmark with keepalive_timeout 65, nginx is<br>
> > very slow (5-20 seconds delay) to accept new connections as soon<br>> > as it reaches 1500 concurrent connections. It plateaus here: it<br>> > completes all the requests but it never exceeds approximately<br>
> > 1500 concurrent connections.<br>><br>> Most likely you hit some network-related limit of your OS or some<br>> firewall inbetween. Check if firewalls have enough number of<br>> state entries, your OS isn't limited by number of sockets, network<br>
> buffers and so on.<br>><br>><br>> Thank you for replying. I should have mentioned, I have tested<br>> with firewall completely disabled and the following sysctls which<br>> I believe should be sufficient.<br>
><br>> net.core.rmem_max = 16777216<br>> net.core.rmem_default = 16777216<br>> net.core.wmem_max = 16777216<br>> net.core.wmem_default = 16777216<br>> net.core.netdev_max_backlog = 262144<br>> net.core.somaxconn = 262144<br>
> net.ipv4.tcp_syncookies = 1<br>> net.ipv4.tcp_max_orphans = 262144<br>> net.ipv4.tcp_max_syn_backlog = 262144<br>> net.ipv4.tcp_synack_retries = 2<br>> net.ipv4.tcp_syn_retries = 2<br>><br>> Is there anything else I can try?<br>
><br>> Thanks!<br>> Steve<br>><br>> Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,61482,61624#msg-61624">http://forum.nginx.org/read.php?2,61482,61624#msg-61624</a><br>><br>><br>> _______________________________________________<br>
> nginx mailing list<br>> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>> <a href="http://nginx.org/mailman/listinfo/nginx">http://nginx.org/mailman/listinfo/nginx</a><br><br><br><br>--<br><a href="http://www.miami-criminallaw.com">http://www.miami-criminallaw.com</a><br>
<br>--<br><br><br><br><br><br>