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
@@ -120,23 +127,18 @@ The table below describes the elements in the above autoscale setting's JSON.
120
127
There are three types of autoscale profiles:
121
128
122
129
- **Default profile:** Use the default profile if you don’t need to scale your resource based on a particular date and time, or day of the week, use a regular or default profile. You can only have one default profile. The sample profile used above is an example of a default profile.
123
-
-
124
130
- **Fixed date profile:** This profile is relevant for a single date and time. Use the fixed date profile to set scaling rules for a specific event. The profile runs only on the event’s date and time. For all other times, autoscale uses the default profile.
125
131
126
132
```json
133
+
...
127
134
"profiles": [
128
135
{
129
136
"name": " regularProfile",
130
137
"capacity": {
131
138
...
132
139
},
133
140
"rules": [
134
-
{
135
141
...
136
-
},
137
-
{
138
-
...
139
-
}
140
142
]
141
143
},
142
144
{
@@ -145,12 +147,7 @@ There are three types of autoscale profiles:
145
147
...
146
148
},
147
149
"rules": [
148
-
{
149
150
...
150
-
},
151
-
{
152
-
...
153
-
}
154
151
],
155
152
"fixedDate": {
156
153
"timeZone": "Pacific Standard Time",
@@ -161,9 +158,86 @@ There are three types of autoscale profiles:
161
158
]
162
159
```
163
160
164
-
- **Recurrence profile:** A recurrence profile is used for a day or set of days of the week. The schema for a recurring profile doesn't include an end date. The end of date and time for a recurring profile is set by the start time of the following profile. When using the portal to configure recurring profiles, the default profile is automatically duplicated, and restarts at the time that you specify for the recurring profile to end. For more information on configuring multiple profiles, see [Autoscale with multiple profiles](./autoscale-multiprofile.md)
165
-
161
+
- **Recurrence profile:** A recurrence profile is used for a day or set of days of the week. The schema for a recurring profile doesn't include an end date. The end of date and time for a recurring profile is set by the start time of the following profile. When using the portal to configure recurring profiles, the default profile is automatically updated to start at the end time that you specify for the recurring profile. For more information on configuring multiple profiles, see [Autoscale with multiple profiles](./autoscale-multiprofile.md)
166
162
163
+
The partial schema example below shows a recurring profile, starting at 06:00 and ending at 19:00 on Saturdays and Sundays. The default profile has been modified to start at 19:00 on Saturdays and Sundays.
"name": "{\"name\":\"Auto created default scale condition\",\"for\":\"Weekend profile\"}",
208
+
"capacity": {
209
+
...
210
+
},
211
+
"recurrence": {
212
+
"frequency": "Week",
213
+
"schedule": {
214
+
"timeZone": "E. Europe Standard Time",
215
+
"days": [
216
+
"Saturday",
217
+
"Sunday"
218
+
],
219
+
"hours": [
220
+
19
221
+
],
222
+
"minutes": [
223
+
0
224
+
]
225
+
}
226
+
},
227
+
"rules": [
228
+
...
229
+
]
230
+
}
231
+
],
232
+
"notifications": [],
233
+
"targetResourceLocation": "eastus"
234
+
}
235
+
236
+
}
237
+
]
238
+
}
239
+
240
+
```
167
241
## Autoscale evaluation
168
242
169
243
Autoscale settings can have multiple profiles. Each profile can have multiple metric rules. Each time the autoscale job runs, it begins by choosing the applicable profile for that time. Then autoscale evaluates the minimum and maximum values, any metric rules in the profile, and decides if a scale action is necessary. The autoscale job runs every 30 to 60 seconds, depending on the resource type.
@@ -182,7 +256,8 @@ The first suitable profile found will be used.
182
256
183
257
After autoscale determines which profile to run, it evaluates the scale-out rules in the profile, that is, where **direction = “Increase”**.
184
258
If one or more scale-out rules are triggered, autoscale calculates the new capacity determined by the **scaleAction** specified for each of those rules. If there's more than one scale-out rule triggered, autoscale scales to the maximum specified capacity to ensure service availability.
185
-
For example, There are two rules: Rule1 specifies scale out by 3 instances and rule 2 specifies scale out by 5. IF Both rules are triggered, autoscale will scale out by 5 instances. Similarly, if one rule specifies scale out by 3 instances and another rule, scale out by 15%, the higher of the two instance counts will be used.
259
+
260
+
For example, assume that there are two rules: Rule1 specifies scale out by 3 instances and rule 2 specifies scale out by 5. If both rules are triggered, autoscale will scale out by 5 instances. Similarly, if one rule specifies scale out by 3 instances and another rule, scale out by 15%, the higher of the two instance counts will be used.
186
261
187
262
If no scale-out rules are triggered, autoscale evaluates all the scale-in rules, that is, rules with **direction = “Decrease”**. Autoscale only scales in if all of the scale-in rules are triggered.
0 commit comments