Autoscaling

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Autoscaling, also spelled auto scaling or auto-scaling, and sometimes also called automatic scaling, is a method used in cloud computing, whereby the amount of computational resources in a server farm, typically measured in terms of the number of active servers, scales automatically based on the load on the farm. It is closely related to, and builds upon, the idea of load balancing.[1][2]

Advantages[edit]

Autoscaling offers the following advantages:

  • For companies running their own web server infrastructure, autoscaling typically means allowing some servers to go to sleep during times of low load, saving on electricity costs (as well as water costs if water is being used to cool the machines).[3]
  • For companies using infrastructure hosted in the cloud, autoscaling can mean lower bills, because most cloud providers charge based on total usage rather than maximum capacity.[4]
  • Even for companies that cannot reduce the total compute capacity they run or pay for at any given time, autoscaling can help by allowing the company to run less time-sensitive workloads on machines that get freed up by autoscaling during times of low traffic.[5]
  • Autoscaling solutions, such as the one offered by Amazon Web Services, can also take care of replacing unhealthy instances and therefore protecting somewhat against hardware, network, and application failures.[6]
  • Autoscaling can offer greater uptime and more availability in cases where production workloads are variable and unpredictable.

Autoscaling differs from having a fixed daily, weekly, or yearly cycle of server use in that it is responsive to actual usage patterns, and thus reduces the potential downside of having too few or too many servers for the traffic load. For instance, if traffic is usually lower at midnight, then a static scaling solution might schedule some servers to sleep at night, but this might result in downtime on a night where people happen to use the Internet more (for instance, due to a viral news event). Autoscaling, on the other hand, can handle unexpected traffic spikes better.[3][7]

Terminology[edit]

In the list below, we use the terminology used by Amazon Web Services (AWS).[8] However, alternative names are noted and terminology that is specific to the names of Amazon services is not used for the names.

Name (used in AWS,[8] unless otherwise noted) Meaning Alternative names (used in Google Cloud Platform,[9] Microsoft Azure,[10] or other platforms)
Instance A single server or machine that is part of the group of machines subject to autoscaling
Autoscaling group The collection of instances subject to autoscaling, along with all the associated policies and state information Managed instance group (Google Cloud Platform)
Size The number of instances currently part of the autoscaling group
Desired capacity (or desired size) The number of instances that the autoscaling group should have at any given point in time. If the size is less than the desired size, the autoscaling group will try to launch (provision and attach) new instances. If the size is more than the desired size, the autoscaling group will try to remove (detach and terminate) instances
Minimum size A number of instances below which the desired capacity is not allowed to fall
Maximum size A number of instances above which the desired capacity is not allowed to rise
Metric A measurement (such as CPU utilization, memory usage, network usage) associated with the autoscaling group, for which a time series of data points is generated regularly. Thresholds for metrics can be used to set autoscaling policies. Metrics can be based on aggregates of metrics for instances of the autoscaling group, or based on load balancers associated with the autoscaling group
Scaling policy (or autoscaling policy) A policy that specifies a change to the autoscaling group's desired capacity (or sometimes, its minimum and maximum size) in response to metrics crossing specific thresholds. Scaling policies can have associated cooldown periods, which prevent additional scaling actions from occurring immediately after a specific scaling action. Changes to desired capacity could be incremental (increase or decrease by a specific number) or could specify a new value of the desired capacity. Policies that increase the desired capacity are called "scaling out" or "scaling up" policies, and policies that decrease the desired capacity are called "scaling in" or "scaling down" policies
Health check A way for the autoscaling group to determine if the instances attached to it are functioning properly. A health check may be based on whether the instance still exists and is reachable, or it could be based on whether the instance is still registered and in service with an associated load balancer
Launch configuration A description of the parameters and scripts used when launching a new instance. This includes the instance type, purchase options (such as spot versus on-demand in the case of AWS), possible availability zones for launch, machine image, and scripts to run on launch Instance template (Google Cloud Platform)
Manual scaling A scaling action executed manually
Scheduled scaling A scaling policy that is executed at a specific time, for instance, time of day or week or month or year. See #Scheduled scaling for more

Practice[edit]

Amazon Web Services (AWS)[edit]

Auto-scaling

Amazon Web Services launched the Amazon Elastic Compute Cloud (EC2) service in August 2006, that allowed developers to programmatically create and terminate instances (machines).[11][12] At the time of initial launch, AWS did not offer autoscaling, but the ability to programmatically create and terminate instances gave developers the flexibility to write their own code for autoscaling.

Third-party autoscaling software for AWS began appearing around April 2008. These included tools by Scalr[13] and RightScale. RightScale was used by Animoto, which was able to handle Facebook traffic by adopting autoscaling.[14][15]

On May 18, 2009, Amazon launched its own autoscaling feature along with Elastic Load Balancing, as part of Amazon Elastic Compute Cloud.[16] Autoscaling is now an integral component of Amazon's EC2 offering.[2][17][18] Autoscaling on Amazon Web Services is done through a web browser or the command line tool.[19]

On-demand video provider Netflix documented their use of autoscaling with Amazon Web Services to meet their highly variable consumer needs. They found that aggressive scaling up and delayed and cautious scaling down served their goals of uptime and responsiveness best.[7]

In an article for TechCrunch, Zev Laderman, the co-founder and CEO of Newvem, a service that helps optimize AWS cloud infrastructure, recommended that startups use autoscaling in order to keep their Amazon Web Services costs low.[4]

Various best practice guides for AWS use suggest using its autoscaling feature even in cases where the load is not variable. That is because autoscaling offers two other advantages: automatic replacement of any instances that become unhealthy for any reason (such as hardware failure, network failure, or application error), and automatic replacement of spot instances that get interrupted for price or capacity reasons, making it more feasible to use spot instances for production purposes.[6][20][21] Netflix's internal best practices require every instance to be in an autoscaling group, and its conformity monkey terminates any instance not in an autoscaling group in order to enforce this best practice.[22]

Microsoft's Windows Azure[edit]

On June 27, 2013, Microsoft announced that it was adding autoscaling support to its Windows Azure cloud computing platform.[23][24][25] Documentation for the feature is available on the Microsoft Developer Network.[10][26]

Oracle Cloud[edit]

Oracle Cloud Platform allows server instances to automatically scale a cluster in or out by defining an auto-scaling rule.[27] These rules are based on CPU and/or memory utilization and determine when to add or remove nodes.

Google Cloud Platform[edit]

On November 17, 2014, the Google Compute Engine announced a public beta of its autoscaling feature for use in Google Cloud Platform applications.[28][29][30][31] As of March 2015, the autoscaling tool is still in Beta.[9]

Facebook[edit]

In a blog post in August 2014, a Facebook engineer disclosed that the company had started using autoscaling to bring down its energy costs. The blog post reported a 27% decline in energy use for low traffic hours (around midnight) and a 10-15% decline in energy use over the typical 24-hour cycle.[3][32]

Kubernetes Horizontal Pod Autoscaler[edit]

Kubernetes Horizontal Pod Autoscaler automatically scales the number of pods in a replication controller, deployment or replicaset based on observed CPU utilization (or, with beta support, on some other, application-provided metrics)[33]

Alternative autoscaling decision approaches[edit]

Autoscaling by default uses reactive decision approach for dealing with traffic scaling: scaling only happens in response to real-time changes in metrics. In some cases, particularly when the changes occur very quickly, this reactive approach to scaling is insufficient. Two other kinds of autoscaling decision approaches are described below.

Scheduled autoscaling approach[edit]

This is an approach to autoscaling where changes are made to the minimum size, maximum size, or desired capacity of the autoscaling group at specific times of day. Scheduled scaling is useful, for instance, if there is a known traffic load increase or decrease at specific times of the day, but the change is too sudden for reactive approach based autoscaling to respond fast enough. AWS autoscaling groups support scheduled scaling.[34]

Predictive autoscaling[edit]

This approach to autoscaling uses predictive analytics. The idea is to combine recent usage trends with historical usage data as well as other kinds of data to predict usage in the future, and autoscale based on these predictions. For parts of their infrastructure and specific workloads, Netflix found that Scryer, their predictive analytics engine, gave better results than Amazon's reactive approach based autoscaling. In particular, it was better for:[35][32]

  • Identifying huge spikes in demand in the near future and getting capacity ready a little in advance
  • Dealing with large-scale outages, such as failure of entire availability zones and regions
  • Dealing with variable traffic patterns, providing more flexibility on the rate of scaling out or in based on the typical level and rate of change in demand at various times of day

See also[edit]

References[edit]

  1. ^ "Above the Clouds: A Berkeley View of Cloud Computing" (PDF). Berkeley EECS. February 10, 2009. Retrieved March 21, 2015. 
  2. ^ a b "Auto Scaling". Amazon Web Services. Retrieved March 21, 2015. 
  3. ^ a b c Wu, Qiang (August 8, 2014). "Making Facebook's software infrastructure more energy efficient with Autoscale". Facebook Code Blog. Retrieved March 21, 2015. 
  4. ^ a b Laderman, Zev (April 22, 2012). "The 10 Biggest Mistakes Made With Amazon Web Services". TechCrunch. Retrieved March 21, 2015. 
  5. ^ Park, Andrew; Denlinger, Darrell; Watson, Coburn (September 18, 2015). "Creating Your Own EC2 Spot Market". Netflix. Retrieved December 16, 2016. 
  6. ^ a b Wittig, Michael (December 26, 2015). "5 AWS mistakes you should avoid". cloudonaut. Retrieved December 16, 2016. 
  7. ^ a b Orzell, Greg; Becker, Justin (January 18, 2012). "Auto Scaling in the Amazon Cloud". Netflix Tech Blog. Retrieved March 21, 2012. 
  8. ^ a b "What Is Auto Scaling?". Amazon Web Services. Retrieved December 16, 2016. 
  9. ^ a b "Autoscaler". Google Cloud Platform. Retrieved March 21, 2015. 
  10. ^ a b "Autoscaling Guidance". Microsoft Developer Network. 
  11. ^ Cubrilovic, Nik (August 24, 2006). "Almost Exclusive: Amazon Readies Utility Computing Service". TechCrunch. Retrieved December 4, 2016. 
  12. ^ Barr, Jeff (August 25, 2006). "Amazon EC2 Beta". Amazon Web Services Blog. Retrieved May 31, 2013. 
  13. ^ Work, Henry (April 3, 2008). "Scalr: The Auto-Scaling Open-Source Amazon EC2 Effort". TechCrunch. Retrieved March 21, 2015. 
  14. ^ Howlett, Dennis (June 25, 2008). "RightScale cloud management extends to MySQL. RightScale, which specializes in cloud computing management for the Amazon Web Services platform today announced support for MySQL Enterprise. The service, which goes live July 1, provides automated deployment, management and scaling, coupled with MySQL Enterprise premium-level support for large database applications". ZDNet. Retrieved December 16, 2016. 
  15. ^ von Eicken, Thorsten (April 23, 2008). "Animoto's Facebook Scale-Up". Retrieved December 16, 2016. 
  16. ^ Barr, Jeff (May 18, 2009). "New Features for Amazon EC2: Elastic Load Balancing, Auto Scaling, and Amazon CloudWatch". Amazon Web Services. Retrieved June 15, 2016. 
  17. ^ "What is autoscaling?". TechTarget. Retrieved March 21, 2015. 
  18. ^ Barr, Jeff (July 30, 2014). "Auto Scaling Update – Lifecycle Management, Standby State, and DetachInstances". Amazon Web Services (official blog). Retrieved March 21, 2015. 
  19. ^ "Auto Scaling Command Line Tool". Amazon Web Services (community-edited page). Retrieved March 21, 2015. 
  20. ^ Adams, Rich (February 3, 2014). "AWS Tips I Wish I'd Known Before I Started. A collection of random tips for Amazon Web Services (AWS) that I wish I'd been told a few years ago, based on what I've learned by building and deploying various applications on AWS". Retrieved December 16, 2016. 
  21. ^ "How to Use Amazon EC2 Spot Instances". wikiHow. Retrieved December 16, 2016. 
  22. ^ "The Netflix Simian Army". Netflix. July 19, 2011. Retrieved December 5, 2016. 
  23. ^ Lardinois, Frederic (June 27, 2013). "Microsoft Adds Auto Scaling To Windows Azure". TechCrunch. Retrieved March 21, 2015. 
  24. ^ "Microsoft to add autoscaling, alerts to Windows Azure". ZDNet. June 27, 2013. Retrieved March 21, 2015. 
  25. ^ Butler, Brandon (August 7, 2013). "Google, Microsoft play catch up to Amazon, add load balancing, auto-scaling to their clouds". Network World. Retrieved March 21, 2015. 
  26. ^ "The Autoscaling Application Block". Microsoft Developer Network. Retrieved March 21, 2015. 
  27. ^ "Administering PaaS Services". Oracle Help Center. Retrieved 2018-05-16. 
  28. ^ Balejko, Filip (November 17, 2014). "Autoscaling, welcome to Google Compute Engine". Google Cloud Platform blog. Retrieved March 21, 2015. 
  29. ^ Protalinski, Emil (November 17, 2014). "Google Compute Engine gets Autoscaler to adjust app resources based on varying traffic and workloads". VentureBeat. Retrieved March 21, 2015. 
  30. ^ Lardinois, Frederic (November 17, 2014). "Google Brings Autoscaling To Compute Engine". TechCrunch. Retrieved March 21, 2015. 
  31. ^ Verge, Jason (November 17, 2014). "Google Launches Autoscaling Beta on Compute Engine". Data Center Knowledge. Retrieved March 21, 2015. 
  32. ^ a b "Autoscaling: How the Cloud Provides a Tremendous Boost". Morpheus. November 2, 2016. Retrieved December 16, 2016. 
  33. ^ "Horizontal Pod Autoscaler Walkthrough". Retrieved June 21, 2018. 
  34. ^ "Scheduled Scaling". Amazon Web Services. Retrieved December 16, 2016. 
  35. ^ Jacobson, Daniel; Yuan, Danny; Joshi, Neeraj. "Scryer: Netflix's Predictive Auto Scaling Engine". The Netflix Tech Blog. Netflix. Retrieved 28 May 2015.