Nginx setting up >25.000 concurrent connections per second

[MagicBear]

here is my server results.
using 3 of ab, each open 10000 concurrent connections.

cat logger | sed  's/||/ /g' | awk '{print $3}'| sed 's/\.[0-9]\+//g'
| sort | uniq -c
  66776 1317949624
  91383 1317949625
  92828 1317949626
  93364 1317949627
  91456 1317949628
  93498 1317949629
  92916 1317949630
  91795 1317949631
  91921 1317949632
  92935 1317949633
  93000 1317949634
  89737 1317949635
  91141 1317949636
  93217 1317949637
  93490 1317949638
  93069 1317949639
  88566 1317949640
  93721 1317949641
  93860 1317949642
  90619 1317949643
  93118 1317949644
  93011 1317949645
  94501 1317949646
  93367 1317949647
  92656 1317949648
  91941 1317949649

using 60% of cpu.
Server Environment:
4x AMD Quad-Core 8360 SE  (total 16 cores)
32G DDR2
SATA3 SSD (r/w 550MB/s)
4x1Gbps Ethernet

2011/10/7 Bradley Falzon <brad at teambrad.net>:
> On Fri, Oct 7, 2011 at 5:00 AM, atadmin <nginx-forum at nginx.us> wrote:
>>
>> # Turn on syncookies for SYN flood attack protection
>> net.ipv4.tcp_syncookies = 0
>
> I've never tested the performance benefit (and the costs) of having sync
> cookies enabled or not, but that command there suggests you have turned sync
> cookies off (you probably want it enabled - again it comes at a cost I
> haven't personally investigated).
>
> Also, you have mentioned the state of iptables connection tracking yet. That
> could be a problem if you believe the bottleneck is the server and haven't
> checked that already. You probably want to disable nf_conntrack and rewrite
> your iptables rules (or just disable firewalling completely).
>
> --
> Bradley Falzon
> brad at teambrad.net
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



-- 
MagicBear