Skip to content

Commit 8d59d7b

Browse files
authored
Update autoscale-azure-api-fhir.md
1 parent 0bd4667 commit 8d59d7b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/healthcare-apis/azure-api-for-fhir/autoscale-azure-api-fhir.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ You can also decrease the max `RU/s` or `Tmax` value. When you lower the max `RU
4949
* **Example 2**: You have 20-GB data and the highest provisioned `RU/s` is 100,000. The minimum value is Max (4000, **100,000/10**, 20x400) = 10,000. The second number, **100,000/10 =10,000**, is used.
5050
* **Example 3**: You have 80-GB data and the highest provisioned RU/s is 300,000. The minimum value is Max (4000, 300,000/10, **80x400**) = 32,000. The third number, **80x400=32,000**, is used.
5151

52-
You can adjust the max `RU/s` or `Tmax` value through the portal if it's a valid number and no greater than 10,000 `RU/s`. You can create a support ticket to request `Tmax` value larger than 10,000.
52+
You can adjust the max `RU/s` or `Tmax` value through the portal if it's a valid number and no greater than 100,000 `RU/s`. You can create a support ticket to request `Tmax` value larger than 100,000.
5353

5454
>[!Note]
5555
>As data storage grows, the system will automatically increase the max throughput to the next highest RU/s that can support that level of storage.

0 commit comments

Comments
 (0)