FWIW - I have found rate limiting very useful (with hardware LB as well as
nginx) but, because of the inherent burstiness of web traffic, I typically set
my threshold to 10x or 20x my expected “reasonable peak rate.”
The rationale is that this is a very crude tool, just one of many that need to
Thank you very much for clearing this out. All I need to do is
"limit_req_log_level warn;" and then I see limits as warn-logs and delaying
as info, and hence I only view warn+ levels, it is omitted from the logfile
completely.
---
Med venlig hilsen / Best Regards
Stephan Ryer Møller
Partner & CTO
Hello!
On Mon, Nov 20, 2017 at 11:33:26AM +0100, Stephan Ryer wrote:
> We are using nginx as a proxy server in front of our IIS servers.
>
> We have a client who needs to call us up to 200 times per second. Due to
> the roundtrip-time, 16 simultanious connections are opened from the client
> and
Hello
We are using nginx as a proxy server in front of our IIS servers.
We have a client who needs to call us up to 200 times per second. Due to
the roundtrip-time, 16 simultanious connections are opened from the client
and each connection is used independently to send a https request, wait for
x
