Skip to content

Commit

Permalink
Merge pull request #2747 from ClickHouse/aashishkohli-patch-4
Browse files Browse the repository at this point in the history
Update scaling.md
  • Loading branch information
justindeguzman authored Nov 1, 2024
2 parents 3cc1435 + cffdd45 commit a1fa391
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions docs/en/cloud/manage/scaling.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,10 @@ Once the service has scaled, the metrics dashboard in the cloud console should s
## Automatic Idling
In the **Settings** page, you can also choose whether or not to allow automatic idling of your service when it is inactive as shown in the image above (i.e. when the service is not executing any user-submitted queries). Automatic idling reduces the cost for your service as you are not billed for compute resources when the service is paused.

:::note
In certain special cases, for instance when a service has a high number of parts, the service will not be idled automatically.
:::

:::danger When not to use automatic idling
Use automatic idling only if your use case can handle a delay before responding to queries, because when a service is paused, connections to the service will time out. Automatic idling is ideal for services that are used infrequently and where a delay can be tolerated. It is not recommended for services that power customer-facing features that are used frequently.
:::
Expand Down

0 comments on commit a1fa391

Please sign in to comment.