Skip to content

Commit 995df06

Browse files
authored
Raising Acrolinx
1 parent 2052525 commit 995df06

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Azure Health Data Services provides a managed service for persisting FHIR-compli
1515

1616
Autoscaling is a capability to dynamically scale your FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscale capability and the process is automated. The capability provides elasticity and enables provisioning of additional instances for customers FHIR service on demand.
1717

18-
The autoscaling feature adjusts computing resources automatically to optimize service scalability. There is no action required from customers.
18+
The autoscaling feature adjusts computing resources automatically to optimize service scalability. There's no action required from customers.
1919

2020
The autoscaling feature for FHIR service is available in all regions where the FHIR service is supported.
2121
> [!NOTE]
@@ -31,7 +31,7 @@ Autoscaling policies defined for FHIR service consists of two parts:
3131

3232
* Scaling mechanism
3333

34-
Scaling Mechanism describes how scaling will be performed when it is triggered. Mechanism is only applied when the conditions from the trigger are met.
34+
Scaling Mechanism describes how scaling will be performed when it's triggered. Mechanism is only applied when the conditions from the trigger are met.
3535
There are three factors that determine when the service will be scaled:
3636

3737
* 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.
@@ -41,7 +41,7 @@ Autoscaling policies defined for FHIR service consists of two parts:
4141
* Scaling interval
4242

4343
Scaling Interval is used determines how often the trigger will be checked. Once the trigger is checked, if scaling is needed the mechanism will be applied. If
44-
scaling is not needed, then no action will be taken. In both cases, trigger will not be checked again before scaling interval expires again. Scaling interval is
44+
scaling isn't needed, then no action will be taken. In both cases, trigger won't be checked again before scaling interval expires again. Scaling interval is
4545
set to 1 minute.
4646

4747
## FAQ

0 commit comments

Comments
 (0)