On 23 Out 2011 20h47 WEST, ilan@time4learning.com wrote:


> I ran them in 2 separate shells concurrently (as best I could) and
> got about the same result, i.e. 10K req. / sec. per each "ab" test,
> so it does look as if the bottleneck is the testing tool.
>
> I would like to see > 50,000 req. / sec. ultimately in a controlled
> testing environment, what is the best way to try and achieve that?
> Running "ab" in "n" different shells at the same time is an option,
> but difficult.

Forget ab. Use httpload/http_load. It uses a single process, hence it
mimics to a certain extent the way Nginx works. It uses select()
though instead of epoll() or kqueue().

Requesting the empty_gif you should get always something north of 20k
req/s on a semi-decent machine.

--- appa

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx