-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing target base scale instance concurrency for queues #41158
Conversation
API change check API changes are not detected in this pull request. |
Hi @alrod. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Hey @alrod Sorry this PR fell through the cracks. Let me rerun CI and see if things will just pass. |
Hi @alrod. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
Hi @alrod. Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing |
/azp run net - storage - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run net - storage - ci |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Looks like pipeline bot is being strict here, because the branch name doesn't start with "feature/*", I wonder if there's a way around it. |
Closed because we merged this PR |
Currently Azure Queues, we’re using
BatchSize
as per instance concurrency. The actual per instance concurrency is given by the formula C = NewBatchThreshhold + BatchSize. For example, when only BatchSize is set to 16 (the maximum value), the instance concurrency is 24. However if both BatchSize=16 and NewBatchThreshold=200, then instance concurrency is 216. Given this, current TBS model is overscale.