Skip to content

Commit 758c37f

Browse files
restructure autoscaling
1 parent 011b431 commit 758c37f

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

deploy-manage/autoscaling.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,3 +29,10 @@ Autoscaling supports:
2929
::::{note}
3030
Autoscaling is not supported on Debian 8.
3131
::::
32+
33+
Find instructions on setting up and managing autoscaling, including supported environments, configuration options, and examples:
34+
35+
* [Autoscaling in {{ece}} and {{ech}}](/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md)
36+
* [Autoscaling in {{eck}}](TODO)
37+
* [Autoscaling deciders](/deploy-manage/autoscaling/autoscaling-deciders.md)
38+
* [Trained model autoscaling](/deploy-manage/autoscaling/trained-model-autoscaling.md)

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ applies_to:
1616

1717
# Autoscaling in {{ece}} and {{ech}}
1818

19+
## Overview [ec-autoscaling-intro]
20+
When you first create a deployment it can be challenging to determine the amount of storage your data nodes will require. The same is relevant for the amount of memory and CPU that you want to allocate to your machine learning nodes. It can become even more challenging to predict these requirements for weeks or months into the future. In an ideal scenario, these resources should be sized to both ensure efficient performance and resiliency, and to avoid excess costs. Autoscaling can help with this balance by adjusting the resources available to a deployment automatically as loads change over time, reducing the need for monitoring and manual intervention.
21+
1922
To learn more about configuring and managing autoscaling, check the following sections:
2023

2124
* [Overview](#ec-autoscaling-intro)
@@ -27,10 +30,6 @@ To learn more about configuring and managing autoscaling, check the following se
2730

2831
You can also have a look at our [autoscaling example](#ec-autoscaling-example), as well as a sample request to [create an autoscaled deployment through the API](#ec-autoscaling-api-example).
2932

30-
31-
## Overview [ec-autoscaling-intro]
32-
When you first create a deployment it can be challenging to determine the amount of storage your data nodes will require. The same is relevant for the amount of memory and CPU that you want to allocate to your machine learning nodes. It can become even more challenging to predict these requirements for weeks or months into the future. In an ideal scenario, these resources should be sized to both ensure efficient performance and resiliency, and to avoid excess costs. Autoscaling can help with this balance by adjusting the resources available to a deployment automatically as loads change over time, reducing the need for monitoring and manual intervention.
33-
3433
::::{note}
3534
Autoscaling is enabled for the Machine Learning tier by default for new deployments.
3635
::::

0 commit comments

Comments
 (0)