From cffdd45ad8f7e80dd81e1eb25c917e1b852fb4e8 Mon Sep 17 00:00:00 2001 From: Aashish Kohli Date: Fri, 1 Nov 2024 12:42:23 -0700 Subject: [PATCH] Update scaling.md --- docs/en/cloud/manage/scaling.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/en/cloud/manage/scaling.md b/docs/en/cloud/manage/scaling.md index 2ca13b3408a..ad49cff3642 100644 --- a/docs/en/cloud/manage/scaling.md +++ b/docs/en/cloud/manage/scaling.md @@ -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. :::