Skip to content

Commit c03ded5

Browse files
committed
Remove the 512 MB option
1 parent d539d1a commit c03ded5

File tree

5 files changed

+6
-8
lines changed

5 files changed

+6
-8
lines changed

articles/azure-functions/flex-consumption-how-to.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -415,10 +415,10 @@ At any point, you can change the instance memory size setting used by your app.
415415

416416
### [Azure CLI](#tab/azure-cli)
417417

418-
This example uses the [`az functionapp scale config set`](/cli/azure/functionapp/scale/config#az-functionapp-scale-config-set) command to change the instance memory size setting to 512 MB:
418+
This example uses the [`az functionapp scale config set`](/cli/azure/functionapp/scale/config#az-functionapp-scale-config-set) command to change the instance memory size setting to 4,096 MB:
419419

420420
```azurecli
421-
az functionapp scale config set --resource-group <resourceGroup> --name <APP_NAME> --instance-memory 512
421+
az functionapp scale config set --resource-group <resourceGroup> --name <APP_NAME> --instance-memory 4096
422422
```
423423

424424
### [Azure portal](#tab/azure-portal)

articles/azure-functions/flex-consumption-plan.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,11 @@ Flex Consumption expands on the traditional benefits of Consumption plan by addi
4848

4949
When you create your function app in a Flex Consumption plan, you can select the memory size of the instances on which your app runs. See [Billing](#billing) to learn how instance memory sizes affect the costs of your function app.
5050

51-
Currently, Flex Consumption offers these instance memory size options: 512 MB, 2,048 MB, and 4,096 MB.
51+
Currently, Flex Consumption offers instance memory size options of both 2,048 MB and 4,096 MB.
5252

5353
When deciding on which instance memory size to use with your apps, here are some things to consider:
5454

55-
+ The 2,048-MB instance memory size is the default and should be used for most scenarios. The 512 MB and 4,096-MB instance memory sizes are available for scenarios that best suit your application's concurrency or processing power requirements. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory).
55+
+ The 2,048-MB instance memory size is the default and should be used for most scenarios. Use the 4,096-MB instance memory size for scenarios where your app requires more concurrency or higher processing power. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory).
5656
+ You can change the instance memory size at any time. For more information, see [Configure instance memory](flex-consumption-how-to.md#configure-instance-memory).
5757
+ Instance resources are shared between your function code and the Functions host.
5858
+ The larger the instance memory size, the more each instance can handle as far as concurrent executions or more intensive CPU or memory workloads. Specific scale decisions are workload-specific.
@@ -116,7 +116,6 @@ Currently, each region in a given subscription has a memory limit of 512,000 MB
116116

117117
| Instance memory size (MB) | Max instance counts (per region) |
118118
| ----- | ---- |
119-
| `512 MB` | 1,000 |
120119
| `2048 MB` | 250 |
121120
| `4096 MB` | 125 |
122121

articles/azure-functions/functions-concurrency.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,6 @@ The Flex Consumption plan scales all HTTP trigger functions together as a group.
3939

4040
| Instance size (MB) | Default concurrency<sup>*</sup> |
4141
| ---- | ---- |
42-
| `512` | `4` |
4342
| `2048` | `16` |
4443
| `4096` | `32` |
4544

articles/azure-functions/monitor-functions-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ These metrics are used to estimate the costs associated with _on demand_ and _al
4141
| **AlwaysReadyFunctionExecutionUnits** | Total MB-millseconds from always ready instances while actively executing functions. | `AlwaysReadyFunctionExecutionUnits / 1,024,000` is the Always Ready Execution Time meter, in GB-seconds. |
4242
| **AlwaysReadyUnits** | The total MB-millseconds of always ready instances assigned to the app, whether or not functions are actively executing. | `AlwaysReadyUnits / 1,024,000` is the Always Ready Baseline meter, in GB-seconds. |
4343

44-
In this table, all execution units are calculated by multipling the fixed instance memory size, such as 512 MB and 2,048 MB, by total execution times, in milliseconds.
44+
In this table, all execution units are calculated by multipling the fixed instance memory size, such as 2,048 MB or 4,096 MB, by total execution times, in milliseconds.
4545

4646
---
4747

includes/functions-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,6 @@ Notes on service limits:
3737
10. Including the production slot.
3838
11. There's currently a limit of 5000 function apps in a given subscription.
3939
12. The Flex Consumption plan is currently in preview.
40-
13. Flex Consumption plan instance sizes are defined as: 512 MB, 2,048 MB, and 4,096 MB. For more information, see [Instance memory](../articles/azure-functions/flex-consumption-plan.md#instance-memory).
40+
13. Flex Consumption plan instance sizes are currently defined as either 2,048 MB or 4,096 MB. For more information, see [Instance memory](../articles/azure-functions/flex-consumption-plan.md#instance-memory).
4141
14. Flex Consumption plan during preview has a regional subscription quota that limits the total memory usage of all instances across a given region. For more information, see [Instance memory](../articles/azure-functions/flex-consumption-plan.md#instance-memory).
4242
15. In a Flex Consumption plan, the host doesn't enforce an execution time limit. However, there are currently no guarantees because the platform might need to terminate your instances during scale-in, deployments, or to apply updates.

0 commit comments

Comments
 (0)