This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
While scaling to 1000 nodes, azure function starts to hang and needs more instances to be in working condition.
PR Checklist
Info on Pull Request
When creating multiple jobs or creating a scaleset with a big size, there is a sudden surge in number of requests. Therefore, waiting for high cpu usage and then auto scaling does do much good. I am scaling rapidly in multiples of 5 and then scaling down slowly to make sure we have required number of instance to work with.
Sorting out the variable names as well because it was hard to find what I was looking for.
Ref. for work is an azure sample repository and azure portal.
Validation Steps Performed
Tested manually on an existing subscription w/o the feature avail, creating a new resource, updating the existing one with the feature avail.