Concurrency Check

**Table 1** Rule details
Parameter	Description
Rule Name	function-graph-concurrency-check
Identifier	Concurrency Check
Description	If the number of concurrent requests allowed by a function is not within the specified amount, this function is non-compliant.
Tag	fgs
Trigger Type	Configuration change
Filter Type	fgs.functions
Rule Parameters	concurrencyLimitLow: the minimum number of concurrent requests. The value must be an integer. concurrencyLimitHigh: the maximum number of concurrent requests. The value must be an integer.

FunctionGraph can concurrently process multiple requests on a single instance. For more information, see Configuring Single-Instance Multi-Concurrency.

Extraordinarily high or low function concurrency may cause the following problems:

High concurrency may cause resource contention, increase the latency and error rate, and even lead to request discarding.
Low concurrency may prolong the request waiting time, affecting user experience. Low concurrency may fail to cope with traffic surges, affecting service continuity.

Set the concurrency for a single instance based on the specified amount and service scenarios. For details, see Configuring Single-Instance Multi-Concurrency.

If FunctionGraph is disabled, the configuration is compliant.
If FunctionGraph is not disabled and the single-instance concurrency is within the specified amount range, the configuration is compliant.
If FunctionGraph is not disabled and the single-instance concurrency is outside the specified amount range, the resource is non-compliant.

If the single-instance concurrency is exactly the boundary value (concurrencyLimitLow or concurrencyLimitHigh), the instance is compliant.