Hi!

Please note that ab itself a huge bottleneck and it gives you zero
information about nginx performance. As you can see you hit the 100% CPU
-what comes from ab load-.
I realized that during performance testing, all what I can tell you: use the
httperf instead if you have a chance.
(do not forget to modify the FD_SETSIZE to higher value)

Regards,
Istvan

2009/4/21 Weibin Yao

> > Just note for everyone: "-c 10" (concurrency 10) is far from real world
> > usage. The select() method used by nginx is poor scaleable for
> concurrency
> > more than 100-200.
> It seems that the most suitable concurrency for my PC is 1-200.
>
> More tests in test case3 for Native Nginx in Windows:
>
> ab.exe -k -n 10000 -c 1 http://127.0.0.1/
> Requests per second: 2424.24 [#/sec] (mean)
> CPU load: about 68%
>
> ab.exe -k -n 10000 -c 10 http://127.0.0.1/
> Requests per second: 2529.64 [#/sec] (mean)
> CPU load: about 67%
>
> ab.exe -k -n 10000 -c 30 http://127.0.0.1/
> Requests per second: 2433.46 [#/sec] (mean)
> CPU load: about 72%
>
> ab.exe -k -n 10000 -c 50 http://127.0.0.1/
> Requests per second: 2397.00 [#/sec] (mean)
> CPU load: about 75%
>
> ab.exe -k -n 10000 -c 75 http://127.0.0.1/
> Requests per second: 2293.91 [#/sec] (mean)
> CPU load: about 77%
>
> ab.exe -k -n 10000 -c 100 http://127.0.0.1/
> Requests per second: 2214.53 [#/sec] (mean)
> CPU load: about 82%
>
> ab.exe -k -n 10000 -c 200 http://127.0.0.1/
> Requests per second: 2184.30 [#/sec] (mean)
> CPU load: about 95%
>
> ab.exe -k -n 10000 -c 300 http://127.0.0.1/
> Requests per second: 1987.58 [#/sec] (mean)
> CPU load: about 99%
>
> ab.exe -k -n 10000 -c 500 http://127.0.0.1/
> Requests per second: 1549.64 [#/sec] (mean)
> CPU load: about 100%
>
> ------------------
> Weibin Yao
> 2009-04-21
>
>
>
>


--
the sun shines for all