Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Autoscaling Azure Function #238

Merged
merged 5 commits into from
Nov 2, 2020
Merged

Conversation

anshuman-goel
Copy link
Contributor

@anshuman-goel anshuman-goel commented Oct 30, 2020

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

  • Applies to work item: Manage Scalesets within pool #124
  • CLA signed. If not, go over here and sign the CLI.
  • Tests added/passed
  • Requires documentation to be updated
  • I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

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.

@bmc-msft
Copy link
Contributor

Performing integration tests

@bmc-msft bmc-msft merged commit 087e6d1 into microsoft:main Nov 2, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Apr 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants