Hi Holgar,
Thanks once again. However, I understand that session means the same as
connection. The rate-limit documentation confirms that: "When the frontend
reaches the specified number of new sessions per second, it stops accepting
*new connections* until the rate drops below the limit again".
Hi Krishna,
Krishna Kumar (Engineering) wrote:
> Thanks for your response. However, I want to restrict the requests
> per second either at the frontend or backend, not session rate. I
> may have only 10 connections from clients, but the backends can
> handle only 100 RPS. How do I deny or delay re
Hi Krishna,
Krishna Kumar (Engineering) wrote:
> What is the way to rate limit on the entire service, without caring
> about which client is hitting it? Something like "All RPS should be <
> 1000/sec"?
You can set a rate limit per frontend (in a frontend section):
rate-limit sessions 1000
Hi Willy, others,
I have seen documents that describe how to rate limit from a single client.
What is the way to rate limit on the entire service, without caring about
which
client is hitting it? Something like "All RPS should be < 1000/sec"?
Thanks,
- Krishna
4 matches
Mail list logo