Skip to content

Commit 386ad3d

Browse files
authored
Merge pull request #104315 from mhoeger/patch-45
Add note about memory limits + node in premium functions
2 parents c1826f1 + c737e1e commit 386ad3d

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

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

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Azure Functions deployed to a Premium plan takes advantage of [new VNet integrat
5353

5454
When assigning a subnet to your function app in a Premium plan, you need a subnet with enough IP addresses for each potential instance. We require an IP block with at least 100 available addresses.
5555

56-
Fore more information, see [integrate your function app with a VNet](functions-create-vnet.md).
56+
For more information, see [integrate your function app with a VNet](functions-create-vnet.md).
5757

5858
### Rapid elastic scale
5959

@@ -90,6 +90,11 @@ When creating or scaling your plan, you can choose between three instance sizes.
9090
|EP2|2|7GB|250GB|
9191
|EP3|4|14GB|250GB|
9292

93+
### Memory utilization considerations
94+
Running on a machine with more memory does not always mean that your function app will use all available memory.
95+
96+
For example, a JavaScript function app is constrained by the default memory limit in Node.js. To increase this fixed memory limit, add the app setting `languageWorkers:node:arguments` with a value of `--max-old-space-size=<max memory in MB>`.
97+
9398
## Regions
9499

95100
Below are the currently supported regions for each OS.

0 commit comments

Comments
 (0)