Skip to content

Commit 0b3c278

Browse files
committed
change h3 to h2 for SEO compliance and github actions build check
1 parent 2b7d991 commit 0b3c278

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,25 +7,25 @@ myst:
77

88
# How does Autoscaling work?
99

10-
### Purpose
10+
## Purpose
1111

1212
Autoscaling ensures dynamic server resource adjustments based on CPU usage metrics, efficiently managing workload demands without manual intervention.
1313

14-
### Configuration Parameters
14+
## Configuration Parameters
1515

1616
In the control panel, users can define autoscaling conditions to tailor actions to their workload demands:
1717
- **CPU Load Threshold:** Specifies the CPU load percentage that triggers autoscaling using a range slider.
1818
- **Minimum Duration:** Determines the minimum duration, in minutes, for the CPU load to exceed the threshold to activate autoscaling.
1919

20-
### Autoscaling Triggering Process
20+
## Autoscaling Triggering Process
2121
- **Continuous Monitoring:** The autoscaling agent continually monitors your application's CPU load.
2222
- **Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user.
2323

24-
### Autoscaling Workflow
24+
## Autoscaling Workflow
2525
- **Initial Cooldown period:** A 5-minute cooldown period after enabling autoscaling prevents rapid scaling due to sudden spikes.
2626
- **Scaling Actions:** Autoscaling automatically upgrades the plan to the next available tier within the same provider, catering to increased demand. The upgraded plan remains effective for 24 hours before reverting to the original configuration.
2727

28-
### Continued Autoscaling Process:
28+
## Continued Autoscaling Process:
2929

3030
If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria:
3131
- **The greater of either**:
@@ -35,10 +35,10 @@ If the server remains overloaded post-autoscaling, the next autoscaling trigger
3535
This approach selects the longer duration between user-defined settings or the fallback duration before initiating the next autoscaling event. It ensures adequate time for evaluating resource changes on CPU performance.
3636
To halt continued autoscaling behavior, simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
3737

38-
### Enabling Autoscaling
39-
For detailed steps on enabling Autoscaling, please refer to our documentation: [How to enable Autoscaling?](how-to-enable-autoscaling.md)
38+
## Enabling Autoscaling
4039

40+
For detailed steps on enabling Autoscaling, please refer to our documentation: [How to enable Autoscaling?](how-to-enable-autoscaling.md)
4141

42-
### Supported providers:
42+
## Supported providers:
4343

4444
Autoscaling is available for Combell Openstack and AWS cloud hosting providers.

0 commit comments

Comments
 (0)