|
| 1 | +--- |
| 2 | +myst: |
| 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. |
| 5 | + title: How does Autoscaling work?? | Hypernode |
| 6 | +--- |
| 7 | + |
| 8 | +# How does Autoscaling work? |
| 9 | + |
| 10 | +### Purpose |
| 11 | + |
| 12 | +Autoscaling ensures dynamic server resource adjustments based on CPU usage metrics, efficiently managing workload demands without manual intervention. |
| 13 | + |
| 14 | +### Configuration Parameters |
| 15 | + |
| 16 | +In the control panel, users can define autoscaling conditions to tailor actions to their workload demands: |
| 17 | +- **CPU Load Threshold:** Specifies the CPU load percentage that triggers autoscaling using a range slider. |
| 18 | +- **Minimum Duration:** Determines the minimum duration, in minutes, for the CPU load to exceed the threshold to activate autoscaling. |
| 19 | + |
| 20 | +### Autoscaling Triggering Process |
| 21 | +- **Continuous Monitoring:** The autoscaling agent continually monitors your application's CPU load. |
| 22 | +- **Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user. |
| 23 | + |
| 24 | +### Autoscaling Workflow |
| 25 | +- **Initial Cooldown period:** A 5-minute cooldown period after enabling autoscaling prevents rapid scaling due to sudden spikes. |
| 26 | +- **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. |
| 27 | + |
| 28 | +### Continued Autoscaling Process: |
| 29 | + |
| 30 | +If the server remains overloaded post-autoscaling, the next autoscaling trigger is determined based on these criteria: |
| 31 | +- **The greater of either**: |
| 32 | + - **User-defined minimum duration for CPU threshold surpassing**: Allows time to assess newly allocated resources' impact on CPU performance. |
| 33 | + - **A fallback duration of 15 minutes**: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes. |
| 34 | + |
| 35 | +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. |
| 36 | +To halt continued autoscaling behavior, simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action. |
| 37 | + |
| 38 | + |
| 39 | +### Supported providers: |
| 40 | + |
| 41 | +Autoscaling is available for Combell Openstack and AWS cloud hosting providers. |
0 commit comments