You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,10 @@
1
1
---
2
2
myst:
3
3
html_meta:
4
-
description: Learn how autoscaling dynamically adjusts server resources based on CPU usage metrics, allowing efficient workload management without manual intervention. Configure thresholds, durations, and understand the workflow for seamless autoscaling on Hypernode.
4
+
description: Learn how autoscaling dynamically adjusts server resources based
5
+
on CPU usage metrics, allowing efficient workload management without manual
6
+
intervention. Configure thresholds, durations, and understand the workflow for
7
+
seamless autoscaling on Hypernode.
5
8
title: How does Autoscaling work? | Hypernode
6
9
---
7
10
@@ -18,20 +21,24 @@ Autoscaling is available for Combell Openstack and AWS cloud hosting providers.
18
21
## Configuration Parameters
19
22
20
23
In the control panel or with CLI tool, users can define autoscaling conditions based on CPU load thresholds and minimum duration to tailor actions to their workload demands:
24
+
21
25
-**CPU Load Threshold:** Specifies the CPU load percentage that triggers autoscaling using a range slider.
22
26
-**Minimum Duration:** Determines the minimum duration, in minutes, for the CPU load to exceed the threshold to activate autoscaling.
23
27
24
28
## Autoscaling Triggering Process
29
+
25
30
-**Continuous Monitoring:** The autoscaling agent continually monitors your application's CPU load.
26
31
-**Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user or default values that were set when the feature was enabled.
27
32
28
33
## Autoscaling Workflow
34
+
29
35
-**Initial Cooldown period:** A 5-minute cooldown period after enabling autoscaling prevents rapid scaling due to sudden spikes.
30
36
-**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.
31
37
32
38
## Continued Autoscaling Process:
33
39
34
40
If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria:
41
+
35
42
-**The greater of either**:
36
43
-**User-defined minimum duration for CPU threshold surpassing**: Allows time to assess newly allocated resources' impact on CPU performance.
37
44
-**A fallback duration of 15 minutes**: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes.
@@ -41,6 +48,7 @@ This approach selects the longer duration between user-defined settings or the f
41
48
To halt continued autoscaling behavior, simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
42
49
43
50
**Important to know:**
51
+
44
52
- For the next 24 hours, plan adjustments are restricted. If necessary, please contact support for assistance.
45
53
- If there are still insufficient resources and the conditions are met, the system will initiate another autoscaling process with a cooldown period of 5 minutes.
46
54
- It will scale up to the largest plan available within the same provider.
0 commit comments