Skip to content

Commit 6b5298e

Browse files
committed
Adding section breaks back in
1 parent aea7a35 commit 6b5298e

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

articles/azure-functions/functions-premium-plan.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,8 @@ $Resource.Properties.minimumElasticInstanceCount = <YOUR_ALWAYS_READY_COUNT>
8080
$Resource | Set-AzResource -Force
8181
```
8282

83+
---
84+
8385
### Pre-warmed instances
8486

8587
Pre-warmed instances is a setting that provides warmed instances as a buffer during HTTP scale and activation events. Pre-warmed instances continue to buffer until the maximum scale-out limit is reached. The default pre-warmed instance count is 1 and, for most scenarios, this value should remain as 1.
@@ -119,6 +121,8 @@ $Resource.Properties.preWarmedInstanceCount = <YOUR_PREWARMED_COUNT>
119121
$Resource | Set-AzResource -Force
120122
```
121123

124+
---
125+
122126
### Maximum function app instances
123127

124128
In addition to the [plan maximum instance count](#plan-and-sku-settings), you can configure a per-app maximum. The app maximum can be configured using the [app scale limit](./event-driven-scaling.md#limit-scale-out).
@@ -175,6 +179,7 @@ You can also increase the maximum burst limit from the Azure PowerShell:
175179
Update-AzFunctionAppPlan -ResourceGroupName <resource_group> -Name <premium_plan_name> -MaximumWorkerCount <desired_max_burst> -Force
176180
```
177181

182+
---
178183
The minimum for every plan will be at least one instance. The actual minimum number of instances will be autoconfigured for you based on the always ready instances requested by apps in the plan. For example, if app A requests five always ready instances, and app B requests two always ready instances in the same plan, the minimum plan size will be calculated as five. App A will be running on all 5, and app B will only be running on 2.
179184

180185
> [!IMPORTANT]
@@ -204,6 +209,8 @@ Increasing the calculated minimum for a plan can be done using the Azure PowerSh
204209
Update-AzFunctionAppPlan -ResourceGroupName <resource_group> -Name <premium_plan_name> -MinimumWorkerCount <desired_min_instances> -Force
205210
```
206211

212+
---
213+
207214
### Available instance SKUs
208215

209216
When creating or scaling your plan, you can choose between three instance sizes. You'll be billed for the total number of cores and memory provisioned, per second that each instance is allocated to you. Your app can automatically scale out to multiple instances as needed.

0 commit comments

Comments
 (0)