Thanks.

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.

Is there a better way?

On Sun, Oct 23, 2011 at 3:00 PM, Stefan Caunter <stef@caunter.ca> wrote:

> Run them in two shells or from two different systems. Also look at wcat.
> BlackBerry PIN 280C6BCD +1 647 459 9475
>
> -----Original Message-----
> From: Ilan Berkner <ilan@time4learning.com>
> Sender: nginx-bounces@nginx.orgDate: Sun, 23 Oct 2011 14:39:08
> To: <nginx@nginx.org>
> Reply-To: nginx@nginx.org
> Subject: Re: Highest requests per second - what is considered top
> performance?
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx