I’ve used the equivalent of nodelay with a rate of 2000 req/sec per IP when a 
retail website was being attacked by hackers. This was in combination with 
microcaching and CDN to protect the back end and endure the site could continue 
to function normally.

Sent from my iPhone

> On Dec 4, 2017, at 1:11 AM, Peter Booth <[email protected]> wrote:
> 
> 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 <[email protected]> wrote:
>> 
>> 
>> For what situation would it be appropriate to use "nodelay"? 
>> 
>>  Original Message  
>> From: [email protected]
>> Sent: December 2, 2017 3:02 AM
>> To: [email protected]
>> Reply-to: [email protected]
>> Subject: Re: Re: How to control the total requests in Ngnix
>> 
>> On Fri, Dec 01, 2017 at 11:18:06AM +0800, [email protected] 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        [email protected]
>> _______________________________________________
>> nginx mailing list
>> [email protected]
>> http://mailman.nginx.org/mailman/listinfo/nginx
>> _______________________________________________
>> nginx mailing list
>> [email protected]
>> http://mailman.nginx.org/mailman/listinfo/nginx
> _______________________________________________
> nginx mailing list
> [email protected]
> http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
[email protected]
http://mailman.nginx.org/mailman/listinfo/nginx

Reply via email to