Skip to content

Commit 16c3587

Browse files
authored
Update fhir-service-autoscale.md
1 parent b92b1f7 commit 16c3587

File tree

1 file changed

+2
-9
lines changed

1 file changed

+2
-9
lines changed

articles/healthcare-apis/fhir/fhir-service-autoscale.md

Lines changed: 2 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,22 +21,15 @@ The autoscaling feature for FHIR service is available in all regions where the F
2121
> [!NOTE]
2222
> Autoscaling feature is subject to the resources availability in Azure regions.
2323
24-
## Autoscaling Policies at Compute level
24+
## Autoscale at Compute level
2525

2626
* Scaling Trigger
2727

2828
Scaling Trigger describes when scaling of the service will be performed. Conditions that are defined in the trigger are checked periodically to determine if a service should be scaled or not. All triggers that are currently supported are Average CPU, Max Worker Thread, Average LogWrite, Average data IO.
2929

3030
* Scaling mechanism
3131

32-
Scaling Mechanism describes how scaling will be performed when it's triggered. Mechanism is only applied when the conditions from the trigger are met.
33-
There are three factors that determine when the service will be scaled:
34-
35-
** Lower load threshold is a value that determines when the service will be scaled in. If the average load of all instances is lower than 20% of CPU usage then the service will be scaled in.
36-
37-
** Upper load threshold is a value that determines when the service will be scaled out. If the average load of all instances is higher than 70% of CPU usage then the service will be scaled out.
38-
39-
** Scaling Interval is used to determine how often the trigger will be checked. Once the trigger is checked, if scaling is needed the mechanism will be applied. Scaling trigger will not be checked before scaling interval expires, which is to set to 1 minute for FHIR service.
32+
The scaling mechanism will only be applied if the trigger check determines that scaling is necessary. Additionally, the scaling trigger will not be evaluated again until the scaling interval has expired, which is set to one minute for FHIR service.
4033

4134
To ensure the best possible outcome, we recommend customers to gradually increase their request rate to match the expected push rate, rather than pushing all requests at once.
4235

0 commit comments

Comments
 (0)