Provides overview of the concept of auto scaling and identifies how to use it to add or remove Cloud Servers or server resources based on the load placed upon your Cloud environment.

Content / Solution:


Auto Scaling is the ability to automatically adjust resources in your Cloud based on load. With Auto Scaling, you have another tool in your toolbox assisting you to control your Cloud more effectively. You can increase resources when they are needed or decrease resources when they are no longer needed.

When you create a Server Farm or Persistence Profile in your MCP 1.0 Cloud Network, you can start and stop the Cloud Servers belonging to that Server Farm automatically using Horizontal Auto Scaling. You also have the ability to configure advanced options like setting the minimum number of Cloud Servers to remain available on each of your Cloud Networks following the execution of the auto scaling actions.

With Vertical Auto Scaling, you can automatically adjust the CPU or RAM resources available to each Cloud Server so your application runs at peak performance. You have the added control to adjust the metric by pre-defined increments. For example, you can scale from 2 CPUs to 4 CPUs or from 4 CPUs to 8 CPUs. You can further refine your Auto Scaling rule using specific timeframes to execute an Auto Scaling action in as little as 5 minutes, up to a maximum of 6 hours.

Since Auto Scaling is dependent on Cloud Monitoring to generate the alerts that trigger the auto scaling actions, it is necessary to enable monitoring for a server before it can be leveraged in Horizontal or Vertical Auto Scaling.

Horizontal vs. Vertical Auto Scaling

Horizontal Auto Scaling allows a user to create a set of rules to start or stop a previously-provisioned Cloud Server assigned to a VIP when a pre-defined monitoring threshold is breached. This allows users to scale the number of servers servicing a VIP up or down based on monitoring results. Horizontal Auto Scaling rules can be created to manage multiple Cloud Servers deployed within the same Server Farm. Horizontal Auto Scaling will not dynamically provision new Cloud Servers. It simply starts and brings into service previously-deployed Cloud Servers that are sitting in a Stopped state (and vice versa).

Vertical Auto Scaling allows a user to create a set of rules to modify the amount of CPU or RAM allocated to an existing Cloud Server when a pre-defined threshold is breached. This allows users to scale the resources associated with a given server based on monitoring results. However, since changes to CPU/RAM require a restart of the server, the server also incurs brief downtime as part of this change.  

Usage & Pricing

The Auto Scaling feature is available for use free of charge. However, Auto Scaling users will be charged for the resources consumed by the monitoring-enabled Cloud Servers participating in both Horizontal and Vertical Auto Scaling.  


As of February 24, 2016 both Horizontal Auto Scaling and  Vertical Auto Scaling are available in both MCP 1.0 and MCP 2.0 locations.


Related Articles: