Skip to content

Commit 089516d

Browse files
Merge pull request #281231 from ggailey777/patch-4
[Functions][Doc Bug] Change `GB` to `MB`
2 parents 157d5e4 + ebd5e41 commit 089516d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -113,10 +113,10 @@ This table shows the language stack versions that are currently supported for Fl
113113

114114
Currently in preview each region in a given subscription has a memory limit of `512,000 MB` for all instances of apps running on Flex Consumption plans. This means that, in a given subscription and region, you could have any combination of instance memory sizes and counts, as long as they stay under the quota limit. For example, each the following examples would mean the quota has been reached and the apps would stop scaling:
115115

116-
+ You have one 2048GB app scaled to 100 and a second 2048GB app scaled to 150 instances
117-
+ You have one 2048GB app that scaled out to 250 instances
118-
+ You have one 4096GB app that scaled out to 125 instances
119-
+ You have one 4096GB app scaled to 100 and one 2048GB app scaled to 50 instances
116+
+ You have one 2,048 MB app scaled to 100 and a second 2,048 MB app scaled to 150 instances
117+
+ You have one 2,048 MB app that scaled out to 250 instances
118+
+ You have one 4,096 MB app that scaled out to 125 instances
119+
+ You have one 4,096 MB app scaled to 100 and one 2,048 MB app scaled to 50 instances
120120

121121
This quota can be increased to allow your Flex Consumption apps to scale further, depending on your requirements. If your apps require a larger quota please create a support ticket.
122122

0 commit comments

Comments
 (0)