Quality Gate worker pool concurrency limits

In high-throughput CI environments, the SonarQube Quality Gate evaluation process can introduce significant latency. When multiple projects trigger analysis simultaneously, the default worker pool size may limit the number of concurrent evaluations, causing subsequent analysis tasks to queue.

This behavior creates a trade-off between maintaining system stability and reducing pull request feedback latency. If the worker queue exceeds capacity, CI pipelines waiting for a Quality Gate status may exceed their predefined timeout thresholds before the evaluation completes.

• What are the specific configuration parameters available to scale the Quality Gate worker pool?
• How does increasing concurrency affect the overall resource consumption of the SonarQube compute engine?