The MSSQL backend currently uses constant-rate polling to find new work to execute. As the number of replicas running this code increases, the load on the MSSQL database increases with it to the point where adding new replicas can reduce overall throughput.
This item tracks doing whatever work is necessary (like dynamically changing polling frequency, etc.) to allow scale-out to as many as 200 replicas sharing a single, fixed-size database while still increasing throughput. The 200 number was chosen to match the Azure Functions maximum replica scale limit.
The MSSQL backend currently uses constant-rate polling to find new work to execute. As the number of replicas running this code increases, the load on the MSSQL database increases with it to the point where adding new replicas can reduce overall throughput.
This item tracks doing whatever work is necessary (like dynamically changing polling frequency, etc.) to allow scale-out to as many as 200 replicas sharing a single, fixed-size database while still increasing throughput. The 200 number was chosen to match the Azure Functions maximum replica scale limit.