You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an orchestration function that performs a fan-out to ~100 activity functions. There are 10 instances in the App Service Plan. Only 1 or 2 instances appear to be picking up work, the other instances are idling. After enabling "Always On", more workers seem to be picking up work from the queue.
Is "Always On" required for Durable Functions to perform correctly on the Dedicated Plan?
For my use-case I'm sharing the App Service Plan with an App/WebJob. The Function App will be invoked about once a day and I'd rather not have it consume memory when not in use. So I'd rather keep "Always On" off for this Function App.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have an orchestration function that performs a fan-out to ~100 activity functions. There are 10 instances in the App Service Plan. Only 1 or 2 instances appear to be picking up work, the other instances are idling. After enabling "Always On", more workers seem to be picking up work from the queue.
Is "Always On" required for Durable Functions to perform correctly on the Dedicated Plan?
For my use-case I'm sharing the App Service Plan with an App/WebJob. The Function App will be invoked about once a day and I'd rather not have it consume memory when not in use. So I'd rather keep "Always On" off for this Function App.
Beta Was this translation helpful? Give feedback.
All reactions