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
Copy file name to clipboardExpand all lines: articles/azure-functions/flex-consumption-how-to.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -446,11 +446,11 @@ You can't currently change the instance memory size setting for your app using V
446
446
## Set always ready instance counts
447
447
448
448
You can set a number of always ready instances for the [Per-function scaling](flex-consumption-plan.md#per-function-scaling) groups or individual functions, to keep your functions loaded and ready to execute. There are three special groups, as in per-function scaling:
449
-
+`http` - all the HTTP triggered functions in the app are scaled together into their own instances.
450
-
+`durable` - all the Durable triggered functions (Orchestration, Activity, Entity) in the app are scaled together into their own instances. Use `durable` as the name for the name value pair setting.
451
-
+`blob` - all the event grid blob storage triggered functions in the app are scaled together into their own instances. Use `blob` as the name for the name value pair setting.
449
+
+`http` - all the HTTP triggered functions in the app scale together into their own instances.
450
+
+`durable` - all the Durable triggered functions (Orchestration, Activity, Entity) in the app scale together into their own instances.
451
+
+`blob` - all the blob (Event Grid) triggered functions in the app scale together into their own instances.
452
452
453
-
Use `http`, `durable` or `blob` as the name for the name value pair setting to configure Always Ready counts for these groups. For all othere trigger types you need to configure Always Ready for each individual function using the format `function:<FUNCTION_NAME>=n`.
453
+
Use `http`, `durable` or `blob` as the name for the name value pair setting to configure always ready counts for these groups. For all other functions in the app you need to configure always ready for each individual function using the format `function:<FUNCTION_NAME>=n`.
1. In your function app page in the [Azure portal](https://portal.azure.com), expand **Settings** in the left menu and select **Scale and concurrency**.
500
500
501
-
1. Under **Always-ready instance minimum** type `http`, `blob`, `durable`, or a specific function name in **Trigger** and type the **Number of always-ready instances**.
501
+
1. Under **Always-ready instance minimum** type `http`, `blob`, `durable`, or a specific function name using the format `function:<FUNCTION_NAME>=n`in **Trigger** and type the **Number of always-ready instances**.
0 commit comments