Gateway current-limiting online are carried out in accordance with the cycle of concurrent algorithms, such as concurrent 100 requests per second, in this case, why not just set the concurrency to 100, a second don't tube is 100 concurrent or two seconds one hundred concurrent, concurrent 100 directly, so what's the problem

CodePudding user response:

Grain size as well, don't set your so-called concurrent number 100, probably get container connection pool's maximum number of connections, but this is for all requests, current-limiting can target a specific services.

Current limit is to ensure that the system will not be a resource consumption/important/not be attack service to sink, granularity is too thick really.