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/functions-premium-plan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ For example, a JavaScript function app is constrained by the default memory limi
151
151
152
152
And for plans with more than 4GB memory, ensure the Bitness Platform Setting is set to `64 Bit` under [General Settings](../app-service/configure-common.md#configure-general-settings).
153
153
154
-
## Region Max Scale Out
154
+
## Region max scale out
155
155
156
156
Below are the currently supported maximum scale-out values for a single plan in each region and OS configuration.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-scale.md
+39-32Lines changed: 39 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.custom: H1Hack27Feb2017
10
10
---
11
11
# Azure Functions hosting options
12
12
13
-
When you create a function app in Azure, you must choose a hosting plan for your app. There are three basic hosting plans available for Azure Functions: [Consumption plan](consumption-plan.md), [Premium plan](functions-premium-plan.md), and [Dedicated (App Service) plan](dedicated-plan.md). All hosting plans are generally available (GA) on both Linux and Windows virtual machines.
13
+
When you create a function app in Azure, you must choose a hosting plan for your app. There are three basic hosting plans available for Azure Functions: [Consumption plan], [Premium plan], and [Dedicated (App Service) plan][Dedicated plan]. All hosting plans are generally available (GA) on both Linux and Windows virtual machines.
14
14
15
15
The hosting plan you choose dictates the following behaviors:
16
16
@@ -29,34 +29,34 @@ The following is a summary of the benefits of the three main hosting plans for F
29
29
30
30
| Plan | Benefits |
31
31
| --- | --- |
32
-
|**[Consumption plan](consumption-plan.md)**| Scale automatically and only pay for compute resources when your functions are running.<br/><br/>On the Consumption plan, instances of the Functions host are dynamically added and removed based on the number of incoming events.<br/><br/> ✔ Default hosting plan.<br/>✔ Pay only when your functions are running.<br/>✔ Scales automatically, even during periods of high load.|
33
-
|**[Premium plan](functions-premium-plan.md)**|Automatically scales based on demand using pre-warmed workers which run applications with no delay after being idle, runs on more powerful instances, and connects to virtual networks. <br/><br/>Consider the Azure Functions Premium plan in the following situations: <br/><br/>✔ Your function apps run continuously, or nearly continuously.<br/>✔ You have a high number of small executions and a high execution bill, but low GB seconds in the Consumption plan.<br/>✔ You need more CPU or memory options than what is provided by the Consumption plan.<br/>✔ Your code needs to run longer than the maximum execution time allowed on the Consumption plan.<br/>✔ You require features that aren't available on the Consumption plan, such as virtual network connectivity.<br/>✔ You want to provide a custom Linux image on which to run your functions. |
34
-
|**[Dedicated plan](dedicated-plan.md)**|Run your functions within an App Service plan at regular [App Service plan rates](https://azure.microsoft.com/pricing/details/app-service/windows/).<br/><br/>Best for long-running scenarios where [Durable Functions](durable/durable-functions-overview.md) can't be used. Consider an App Service plan in the following situations:<br/><br/>✔ You have existing, underutilized VMs that are already running other App Service instances.<br/>✔ Predictive scaling and costs are required.|
32
+
|**[Consumption plan]**| Scale automatically and only pay for compute resources when your functions are running.<br/><br/>On the Consumption plan, instances of the Functions host are dynamically added and removed based on the number of incoming events.<br/><br/> ✔ Default hosting plan.<br/>✔ Pay only when your functions are running.<br/>✔ Scales automatically, even during periods of high load.|
33
+
|**[Premium plan]**|Automatically scales based on demand using pre-warmed workers which run applications with no delay after being idle, runs on more powerful instances, and connects to virtual networks. <br/><br/>Consider the Azure Functions Premium plan in the following situations: <br/><br/>✔ Your function apps run continuously, or nearly continuously.<br/>✔ You have a high number of small executions and a high execution bill, but low GB seconds in the Consumption plan.<br/>✔ You need more CPU or memory options than what is provided by the Consumption plan.<br/>✔ Your code needs to run longer than the maximum execution time allowed on the Consumption plan.<br/>✔ You require features that aren't available on the Consumption plan, such as virtual network connectivity.<br/>✔ You want to provide a custom Linux image on which to run your functions. |
34
+
|**[Dedicated plan]**|Run your functions within an App Service plan at regular [App Service plan rates](https://azure.microsoft.com/pricing/details/app-service/windows/).<br/><br/>Best for long-running scenarios where [Durable Functions](durable/durable-functions-overview.md) can't be used. Consider an App Service plan in the following situations:<br/><br/>✔ You have existing, underutilized VMs that are already running other App Service instances.<br/>✔ Predictive scaling and costs are required.|
35
35
36
36
The comparison tables in this article also include the following hosting options, which provide the highest amount of control and isolation in which to run your function apps.
37
37
38
38
| Hosting option | Details |
39
39
| --- | --- |
40
-
|**[ASE](dedicated-plan.md)**| App Service Environment (ASE) is an App Service feature that provides a fully isolated and dedicated environment for securely running App Service apps at high scale.<br/><br/>ASEs are appropriate for application workloads that require: <br/><br/>✔ Very high scale.<br/>✔ Full compute isolation and secure network access.<br/>✔ High memory usage.|
41
-
|**Kubernetes**<br/>([Direct](functions-kubernetes-keda.md) or<br/>[Azure Arc](../app-service/overview-arc-integration.md)) | Kubernetes provides a fully isolated and dedicated environment running on top of the Kubernetes platform.<br/><br/> Kubernetes is appropriate for application workloads that require: <br/>✔ Custom hardware requirements.<br/>✔ Isolation and secure network access.<br/>✔ Ability to run in hybrid or multi-cloud environment.<br/>✔ Run alongside existing Kubernetes applications and services.|
40
+
|**[ASE][Dedicated plan]**| App Service Environment (ASE) is an App Service feature that provides a fully isolated and dedicated environment for securely running App Service apps at high scale.<br/><br/>ASEs are appropriate for application workloads that require: <br/><br/>✔ Very high scale.<br/>✔ Full compute isolation and secure network access.<br/>✔ High memory usage.|
41
+
|**Kubernetes**<br/>([Direct][Kubernetes] or<br/>[Azure Arc](../app-service/overview-arc-integration.md)) | Kubernetes provides a fully isolated and dedicated environment running on top of the Kubernetes platform.<br/><br/> Kubernetes is appropriate for application workloads that require: <br/>✔ Custom hardware requirements.<br/>✔ Isolation and secure network access.<br/>✔ Ability to run in hybrid or multi-cloud environment.<br/>✔ Run alongside existing Kubernetes applications and services.|
42
42
43
43
The remaining tables in this article compare the plans on various features and behaviors. For a cost comparison between dynamic hosting plans (Consumption and Premium), see the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/). For pricing of the various Dedicated plan options, see the [App Service pricing page](https://azure.microsoft.com/pricing/details/app-service/windows/).
44
44
45
45
## Operating system/runtime
46
46
47
-
The following table shows operating system and language support for the hosting plans.
47
+
The following table shows operating system and [language support](supported-languages.md) for the hosting plans.
|**[Consumption plan]**|C#<br/>JavaScript<br/>Java<br/>Python<br/>PowerShell Core<br/>TypeScript | C#<br/>JavaScript<br/>Java<br/>PowerShell Core<br/>TypeScript | No support |
@@ -65,25 +65,27 @@ The following table shows operating system and language support for the hosting
65
65
66
66
The following table compares the scaling behaviors of the various hosting plans.
67
67
68
-
| Plan | Scale out | Max # instances |
68
+
| Plan | Scale out | Max # instances |
69
69
| --- | --- | --- |
70
-
|**[Consumption plan](consumption-plan.md)**|[Event driven](event-driven-scaling.md). Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding additional instances of the Functions host, based on the number of incoming trigger events. | 200|
71
-
|**[Premium plan](functions-premium-plan.md)**|[Event driven](event-driven-scaling.md). Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding additional instances of the Functions host, based on the number of events that its functions are triggered on. |100|
|**[Kubernetes](functions-kubernetes-keda.md)**| Event-driven autoscale for Kubernetes clusters using [KEDA](https://keda.sh). | Varies by cluster |
70
+
|**[Consumption plan]**|[Event driven](event-driven-scaling.md). Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding additional instances of the Functions host, based on the number of incoming trigger events. |**Windows:**200<br/>**Linux:** 100<sup>1</sup> |
71
+
|**[Premium plan]**|[Event driven](event-driven-scaling.md). Scale out automatically, even during periods of high load. Azure Functions infrastructure scales CPU and memory resources by adding additional instances of the Functions host, based on the number of events that its functions are triggered on. |**Windows:**100<br/>**Linux:** 20-40<sup>2</sup>|
|**[Kubernetes]**| Event-driven autoscale for Kubernetes clusters using [KEDA](https://keda.sh). | Varies by cluster |
75
75
76
-
<sup>1</sup> For specific limits for the various App Service plan options, see the [App Service plan limits](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits).
76
+
<sup>1</sup> During scale out, there's currently a limit of 500 instances per subscription per hour for Linux apps on a Consumption plan. <br/>
77
+
<sup>2</sup> In some regions, Linux apps on a Premium plan can scale to 40 instances. For more information, see the [Premium plan article](functions-premium-plan.md#region-max-scale-out). <br/>
78
+
<sup>3</sup> For specific limits for the various App Service plan options, see the [App Service plan limits](../azure-resource-manager/management/azure-subscription-service-limits.md#app-service-limits).
77
79
78
80
## Cold start behavior
79
81
80
82
| Plan | Details |
81
83
| -- | -- |
82
-
|**[Consumption plan](consumption-plan.md)**| Apps may scale to zero when idle, meaning some requests may have additional latency at startup. The consumption plan does have some optimizations to help decrease cold start time, including pulling from pre-warmed placeholder functions that already have the function host and language processes running. |
83
-
|**[Premium plan](functions-premium-plan.md)**| Perpetually warm instances to avoid any cold start. |
84
-
|**[Dedicated plan](dedicated-plan.md)**| When running in a Dedicated plan, the Functions host can run continuously, which means that cold start isn't really an issue. |
85
-
|**[ASE](dedicated-plan.md)**| When running in a Dedicated plan, the Functions host can run continuously, which means that cold start isn't really an issue. |
86
-
| **[Kubernetes](functions-kubernetes-keda.md)** | Depending on KEDA configuration, apps can be configured to avoid a cold start. If configured to scale to zero, then a cold start is experienced for new events.
84
+
|**[Consumptionplan]**| Apps may scale to zero when idle, meaning some requests may have additional latency at startup. The consumption plan does have some optimizations to help decrease cold start time, including pulling from pre-warmed placeholder functions that already have the function host and language processes running. |
85
+
|**[Premium plan]**| Perpetually warm instances to avoid any cold start. |
86
+
|**[Dedicated plan]**| When running in a Dedicated plan, the Functions host can run continuously, which means that cold start isn't really an issue. |
87
+
|**[ASE][Dedicated plan]**| When running in a Dedicated plan, the Functions host can run continuously, which means that cold start isn't really an issue. |
88
+
| **[Kubernetes]** | Depending on KEDA configuration, apps can be configured to avoid a cold start. If configured to scale to zero, then a cold start is experienced for new events.
87
89
88
90
## Service limits
89
91
@@ -97,13 +99,18 @@ The following table compares the scaling behaviors of the various hosting plans.
97
99
98
100
| Plan | Details |
99
101
| --- | --- |
100
-
|**[Consumption plan](consumption-plan.md)**| Pay only for the time your functions run. Billing is based on number of executions, execution time, and memory used. |
101
-
|**[Premium plan](functions-premium-plan.md)**| Premium plan is based on the number of core seconds and memory used across needed and pre-warmed instances. At least one instance per plan must be kept warm at all times. This plan provides the most predictable pricing. |
102
-
|**[Dedicated plan](dedicated-plan.md)**| You pay the same for function apps in an App Service Plan as you would for other App Service resources, like web apps.|
103
-
|**[App Service Environment (ASE)](dedicated-plan.md)**| There's a flat monthly rate for an ASE that pays for the infrastructure and doesn't change with the size of the ASE. There's also a cost per App Service plan vCPU. All apps hosted in an ASE are in the Isolated pricing SKU. |
104
-
|**[Kubernetes](functions-kubernetes-keda.md)**| You pay only the costs of your Kubernetes cluster; no additional billing for Functions. Your function app runs as an application workload on top of your cluster, just like a regular app. |
102
+
|**[Consumption plan]**| Pay only for the time your functions run. Billing is based on number of executions, execution time, and memory used. |
103
+
|**[Premium plan]**| Premium plan is based on the number of core seconds and memory used across needed and pre-warmed instances. At least one instance per plan must be kept warm at all times. This plan provides the most predictable pricing. |
104
+
|**[Dedicated plan]**| You pay the same for function apps in an App Service Plan as you would for other App Service resources, like web apps.|
105
+
|**[App Service Environment (ASE)][Dedicated plan]**| There's a flat monthly rate for an ASE that pays for the infrastructure and doesn't change with the size of the ASE. There's also a cost per App Service plan vCPU. All apps hosted in an ASE are in the Isolated pricing SKU. |
106
+
|**[Kubernetes]**| You pay only the costs of your Kubernetes cluster; no additional billing for Functions. Your function app runs as an application workload on top of your cluster, just like a regular app. |
105
107
106
108
## Next steps
107
109
108
110
+[Deployment technologies in Azure Functions](functions-deployment-technologies.md)
0 commit comments