I’m a situation where you are confident that the workload is coming from a DDOS attack and not a real user.

For this example the limit is very low and nodelay wouldn’t seem appropriate. If you look at the techempower benchmark results you can see that a single vote VM should be able to serve over 10,000 requests per sec.

Sent from my iPhone

> On Dec 3, 2017, at 4:08 PM, Gary <lists@lazygranch.com> wrote:
>
>
> For what situation would it be appropriate to use "nodelay"?
>
> Original Message
> From: francis@daoine.org
> Sent: December 2, 2017 3:02 AM
> To: nginx@nginx.org
> Reply-to: nginx@nginx.org
> Subject: Re: Re: How to control the total requests in Ngnix
>
> On Fri, Dec 01, 2017 at 11:18:06AM +0800, tongshushan@migu.cn wrote:
>
> Hi there,
>
> Others have already given some details, so I'll try to put everything
> together.
>
> <snip>
>
>> limit_req zone=all burst=100 nodelay;
>
> "block" can be "return error immediately", or can be "delay until the
> right time", depending on what you configure. "nodelay" above means
> "return error immediately".
>
>
> <snip>
>
>
> f
> --
> Francis Daly francis@daoine.org
> _______________________________________________
> 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