microsoft / microsoft/durabletask-mssql
Support scale-out to 200 replicas
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named; start by locating the MSSQL constant-rate polling implementation and measuring database load and throughput as replica counts increase. Done means supporting up to 200 replicas against one fixed-size database while adding replicas continues to increase throughput.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100